her and
allow scripting emacs with python ;-)
But I don't have a magic wand, and it doesn't seem likely that emacs will
ever be scriptable with python. Unless some hero steps up Leo in emacs
will remain a tantalizing possibility, just out of reach.
Edward
--
You received this message because
On Friday, August 2, 2019 at 7:58:19 AM UTC-5, Edward K. Ream wrote:
Org babel is great for code snippets. It does not scale up to entire
> source files.
>
One could consider allowing @others and section references within
part of code blocks
o write the required elisp code*. Indeed, it would be a
big distraction for me and Leo's other devs. However, I am willing to
support such efforts with design suggestions.
#1026: Embed Leo in Emacs
<https://github.com/leo-editor/leo-editor/issues/1026> has been closed and
marked "won't
On Tue, Jul 9, 2019 at 12:20 AM Matt Wilkie wrote:
> Btw, even if Leo's body pane *were* vim, IPC would still be needed
>> between Leo and vim.
>>
>
> This sentence made me wonder: how is IPC or it's analog different from
> what's used within Leo: from outline to body, from Altix (Alt-x) to
>
>
> Btw, even if Leo's body pane *were* vim, IPC would still be needed
> between Leo and vim.
>
This sentence made me wonder: how is IPC or it's analog different from
what's used within Leo: from outline to body, from Altix (Alt-x) to
outline, from body to Render, etc.? Every 'dock' a module
On Tuesday, June 25, 2019 at 9:41:57 AM UTC-5, Edward K. Ream wrote:
>
> On Tue, Jun 25, 2019 at 8:18 AM jkn wrote:
>
> To my mind it would be nicer to have the body pane of Leo visible, but
>> actually *be* the vim, emacs or whatever buffer.
>>
>
> Sure. Alas, I know of no way of doing it.
On Tue, Jun 25, 2019 at 8:18 AM jkn wrote:
Aren't there some ... systems where you can provide (terminology showing
> the vintage here) a handle to an outside program, of 'the window under
> consideration'?
>
Sure. nvim supports servername. See also nvr
Aren't there some ... systems where you can provide (terminology showing
the vintage here) a handle to an outside program, of 'the window under
consideration'?
To my mind it would be nicer to have the body pane of Leo visible, but
actually *be* the vim, emacs or whatever buffer.
In your
On Tue, Jun 25, 2019 at 7:08 AM gar wrote:
Edward, but does Leo need these hard to implement features?
>
No. Leo could be said to be "perfect", just the way it is :-)
> What would Leo achieve when it get them?
>
vim and emacs users who want Leonine features while retaining features of
vim and
with the cursor in the proper place.
>
> *In Vim*: `:leo` transfers control to Leo, updating c.p.b and putting
> focus in the outline.
>
> Similarly, in emacs, leo.
>
> This would let Leonistas to use the *real* vim (or neovim, or emacs) for
> text editing.
>
> *Discus
On Wednesday, June 19, 2019 at 10:29:28 PM UTC-5, Jeff R. wrote:
I have moved off of Leo and now use Emacs, mostly for org-mode but also for
> whatever else is useful. Emacs itself has features that I can't give up, or
> at least am not willing to right now.
>
What are those features? Adding
macs.html>.
There is also an xemacs.py plugin that allows communication between Leo and
emacs.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
I tried Leo a few times and really liked it. Not a programmer, but have to
sort a lot of information and academic writing. I read this list because I
enjoy seeing the project development and enjoy Edward's leadership.
I have moved off of Leo and now use Emacs, mostly for org-mode but also for
On Sun, Jan 5, 2014 at 12:05 PM, gatesphere gatesph...@gmail.com wrote:
To help with this process, I've renamed the current github leo-editor repo
to leo-editor-mirror, so that the true repo can now occupy leo-editor, when
it is created. I've also updated all the scripting and ReadTheDocs
Is the git repo up in github? I can't see it under
https://github.com/leo-editor
Is it open to public?
Thanks
Jack
On Friday, January 3, 2014 11:55:56 PM UTC-5, Terry wrote:
gf's post made me realize my reposting of Ville's reposting failed,
here it is - question for you Jacob / Matt...
On 1/10/2014 9:35 AM, Jack Kuan wrote:
Is the git repo up in github? I can't see it under
https://github.com/leo-editor
Is it open to public?
It's just for testing at the moment. Any changes pushed to the repo
will be blown away when the final migration happens. It's also already
several
I've read so much on rebase vs merge vs grafting vs subtrees vs stitching
and so on that I'm more confused now than when I started. :)
I give up on conjoining the historical repos, let alone current. The idea
of being able to seamlessly follow a feature's changes from now back to the
earliest
On Sat, Jan 4, 2014 at 10:18 AM, Matt Wilkie map...@gmail.com wrote:
this is a more informative starting point
http://stackoverflow.com/questions/19930832/converting-big-bzr-repository-to-git-what-to-expect.
Initial experiments look like it won't be too bad. I'll have more to report
later.
Yes, bzr trunk will be enough for main git repo, and it's not like we would
be deleting the old repos in the process.
On Jan 5, 2014 1:50 PM, Edward K. Ream edream...@gmail.com wrote:
On Sat, Jan 4, 2014 at 10:18 AM, Matt Wilkie map...@gmail.com wrote:
this is a more informative starting point
To help with this process, I've renamed the current github leo-editor
repo to leo-editor-mirror, so that the true repo can now occupy
leo-editor, when it is created. I've also updated all the scripting and
ReadTheDocs settings to reflect this.
Once the migration to git is complete, I'll
On Sun, Jan 5, 2014 at 10:05 AM, gatesphere gatesph...@gmail.com wrote:
Matt, I saw the leo-cvs-2002-2006 repo -- are you going to do different
repos for different points in Leo's history? If so, we could probably get
the leo-editor repo with just bzr's history up and running fairly quickly,
On 1/5/2014 1:47 PM, Matt Wilkie wrote:
On Sun, Jan 5, 2014 at 10:05 AM, gatesphere gatesph...@gmail.com
mailto:gatesph...@gmail.com wrote:
Matt, I saw the leo-cvs-2002-2006 repo -- are you going to do
different repos for different points in Leo's history? If so, we
could
On Sun, 5 Jan 2014 10:47:00 -0800
Matt Wilkie map...@gmail.com wrote:
I've been looking
at Pushing to https://github.com/leo-editor/leo-cvs-2002-2006.git; for 2
hours now. (not frozen, cpu and ram % for git is bouncing slowly up and
down).
Are you using DSL? I get 1.1 Mb / sec. downloand
Well, at the moment, I'm trying to convince bzr that it does indeed know
how to do 'fast-export'...
:) make sure you have gobs of free space, the raw bzr export file for
2002-2006 is 3.2GB.
-matt
--
You received this message because you are subscribed to the Google Groups
leo-editor
On Sun, Jan 5, 2014 at 10:53 AM, Terry Brown terry_n_br...@yahoo.comwrote:
I get 1.1 Mb / sec. downloand :-) but 87 Kb / sec.
upload
good point. I was thinking of standard dnld speeds. Unfortunately I've no
idea what the upload payload size is. I think Jake's idea of breaking
things into
Well, I don't think we want a 3 gig repository for daily work.
On Sun, Jan 5, 2014 at 9:42 PM, Matt Wilkie map...@gmail.com wrote:
On Sun, Jan 5, 2014 at 10:53 AM, Terry Brown terry_n_br...@yahoo.comwrote:
I get 1.1 Mb / sec. downloand :-) but 87 Kb / sec.
upload
good point. I was
On 1/5/2014 2:42 PM, Matt Wilkie wrote:
On Sun, Jan 5, 2014 at 10:53 AM, Terry Brown terry_n_br...@yahoo.com
mailto:terry_n_br...@yahoo.com wrote:
I get 1.1 Mb / sec. downloand :-) but 87 Kb / sec.
upload
good point. I was thinking of standard dnld speeds. Unfortunately I've
no
On 1/5/2014 2:42 PM, Matt Wilkie wrote:
On Sun, Jan 5, 2014 at 10:53 AM, Terry Brown terry_n_br...@yahoo.com
mailto:terry_n_br...@yahoo.com wrote:
I get 1.1 Mb / sec. downloand :-) but 87 Kb / sec.
upload
good point. I was thinking of standard dnld speeds. Unfortunately I've
no
On Sun, Jan 5, 2014 at 12:59 PM, gatesphere gatesph...@gmail.com wrote:
I just pushed ~9000 commits (commits in branches on launchpad are
apparently visible in the mainline repo when importing to git) to the
leo-bzr-test repo (https://github.com/leo-editor/leo-bzr-test), and it
took me a
On 1/5/2014 4:56 PM, Matt Wilkie wrote:
Thank you very much Jake. Clearly something was wrong on my end! I
followed your example and had a successful push within 20 minutes
(including repacking and pruning; on-disk size of the repo shrank from
750mb to 63mb.).
Glad to see it worked!
After
On Friday, January 3, 2014 10:55:56 PM UTC-6, Terry wrote:
bzr is more than enough DVCS for Leo, the only drawback is Ohh, you're
not using git
Longer term bzr may atrophy, I guess, although I imagine it will be
usable for many years to come.
I agree. Leo should move to git
On Fri, Jan 3, 2014 at 8:55 PM, Terry Brown terry_n_br...@yahoo.com wrote:
Matt and Jacob - it seemed that between you you'd kind of done most of
the leg-work for getting Leo's VCS history in one place and moving it
to git
Jake has done all of the git and github work on Leo itself. I've just
this is a more informative starting point
http://stackoverflow.com/questions/19930832/converting-big-bzr-repository-to-git-what-to-expect.
Initial experiments look like it won't be too bad. I'll have more to report
later.
-matt
On Sat, Jan 4, 2014 at 7:18 AM, Matt Wilkie map...@gmail.com wrote:
On 1/3/2014 11:55 PM, Terry Brown wrote:
Matt and Jacob - it seemed that between you you'd kind of done most of
the leg-work for getting Leo's VCS history in one place and moving it
to git - I'm not saying we should move right now, but just wondering
how high the barrier is, not very, perhaps?
Pulling the years 2002-2006 into git went smoothly enough, following the
guide linked previously, but 2006-2008 is giving some trouble. The
Launchpad auto-import version of this repo drops all the tags (e.g.
v4.4.1) which is important history IMO, and has a different parent
directory than the
gf's post made me realize my reposting of Ville's reposting failed,
here it is - question for you Jacob / Matt...
Begin forwarded message:
On Thu, 02 Jan 2014 07:45:25 -0800 (PST)
Ville Vainio (Google+) noreply-7dc29...@plus.google.com wrote:
On Fri, May 13, 2011 at 4:45 AM, Gour-Gadadhara Dasa g...@atmarama.net wrote:
Now, since I regularly use Emacs as my preferred editor, I wonder what
would be some of pro/cons in using only Leo for editing body text
or editing body text with Emacs?
You can use Emacs to edit Leo sources using
Hello!
Soon I plan to start writing on PyQT application and considering that,
so far, I'm the only one working on it, it's a nice opportunity to use
Leo with @file not caring much about sentinels and later
collaboration.
Now, since I regularly use Emacs as my preferred editor, I wonder what
On Fri, May 13, 2011 at 12:45 PM, Gour-Gadadhara Dasa g...@atmarama.net wrote:
Soon I plan to start writing on PyQT application and considering that,
so far, I'm the only one working on it, it's a nice opportunity to use
Leo with @file not caring much about sentinels and later
collaboration.
in Leo for e.g. PHP?
OTOH, editors like komodo edit have a more sophisticated
autocompletion than Leo has (so far, at least until my summer holiday
starts ;-).
I considered Eric (due to PyQt), but was told that it does not bring
much over Emacs.
What do you think about it?
Leo with(out
40 matches
Mail list logo
