I assume all *nix shell users use the screen shell multiplexer,
and hopefully *nix shell users who use Leo know about the leoscreen
plugin which passes text back and forth between Leo and the shell
(provided you're running screen), which is very handy for build scripts
and SQL hacking etc. etc.
A
On Wed, 16 May 2012 12:46:14 -0700 (PDT)
"Edward K. Ream" wrote:
> At present, the leo/external/codewise.py and leo/core/leoInspect.py
> files duplicates code from leoGlobals.py so that these files can be
> executed in contexts where leo.core.leoGlobals can not be imported
> conveniently.
>
> Ho
Many, many writers already appreciate outlines. After I figured out
how to bind reSt to hotkeys (thanks Edward), I have been using it
happily and creatively. It would be an easy sell to writers if the
learning curve was less steep. The massive configurability
(programmability) of Leo will put off a
At present, the leo/external/codewise.py and leo/core/leoInspect.py
files duplicates code from leoGlobals.py so that these files can be
executed in contexts where leo.core.leoGlobals can not be imported
conveniently.
However, this duplication of code is extremely ugly and fragile: fixes
to leoGlob
On May 16, 11:34 am, "Edward K. Ream" wrote:
> I have just spent over an hour reorganizing Leo's to-do list.
Rev 5306 contains another reorg. leoToDo.txt now contains the entire
to-do list. It is organized into "will do", "might do" and "won't do"
parts. The "To do: 4.10.1" list is the "will d
I'm not sure selling outlines is a right approach.
It's better to try to sell Leo to people that already appreciate outlines.
On May 16, 2012 6:16 PM, "Edward K. Ream" wrote:
> On Wed, May 16, 2012 at 10:05 AM, Terry Brown
> wrote:
>
> >> We have *got* to link to this video from Leo's home pag
Incremental improvements to Leo will continue. Indeed, I have just
spent over an hour reorganizing Leo's to-do list, emphasizing items
that will make a real difference to users. I expect eventually to
complete all the items in leoToDo.txt, with the exception of those
labelled "vague".
>From time
On Wed, May 16, 2012 at 10:05 AM, Terry Brown wrote:
>> We have *got* to link to this video from Leo's home page.
>
> I'm not sure it's ideal, over an hour long and starts of with a lot of
> banter about programming and so on - something shorter and jumping in
> to the core issue sooner would be
On Wed, 16 May 2012 06:50:24 -0700 (PDT)
"Edward K. Ream" wrote:
> We have *got* to link to this video from Leo's home page.
I'm not sure it's ideal, over an hour long and starts of with a lot of
banter about programming and so on - something shorter and jumping in
to the core issue sooner would
For the last few days I have been playing with vim and Leo's vim
bindings. This post will discuss my explorations and conclusions.
To state my conclusions first:
1. Vim-like bindings are not something I will never be comfortable
with.
2. It might be possible to support, for example, the functio
10 matches
Mail list logo
