Re: Leo as Personal Information Manager: multiple nodes in the body pane?

I think this makes sense, and has been addressed a couple of times. First a terminology issue: the body pane edits the body of a node, what you're looking for is a pane which lets you edit the bodies (and maybe headlines) of multiple nodes at once, which would a pane with a different name,

Leo as Personal Information Manager: multiple nodes in the body pane?

Hi! I'm getting started with Leo as a personal information manager, and I like it a lot. The option to have clones of notes which stay in sync is very powerful. I do have a usability problem with it: I very often have small sections, e.g. a paragraph, that I want to be able to reuse somewhere

Re: The tools I use in Leo all the time

On Fri, Nov 4, 2016 at 9:46 AM, Edward K. Ream wrote: I use the following tools constantly. I won't rank them, but each > contributes significantly: > ​And behind everything is python. It *never* gets in my way. It's always a joy. EKR -- You received this message

Re: ENB: Leo's line-oriented importers: the last collapse in complexity

On Friday, November 4, 2016 at 9:33:04 AM UTC-5, Edward K. Ream wrote: > > On Fri, Nov 4, 2016 at 3:03 AM, Edward K. Ream > wrote: > > Here, I'll write down my initial plan for a remarkable collapse in the complexity of the code. In another related thread

The tools I use in Leo all the time

My rate of programming has accelerated greatly recently. In part, this is because I have realize just how big a privilege it is to be able to continue my life's work. But Leonine tools are also a big part of the picture. I use the following tools constantly. I won't rank them, but each

Leo as a stash manager

Copying whole trees (normal copy, not cloned copy) is a much better way of stashing code that using git stash. I found this out just now when I forgot to copy the new Target class. I had used git stash on some failing code that contained the Target class, so I did a git stash pop. That

Re: ENB: Leo's line-oriented importers: the last collapse in complexity

On Fri, Nov 4, 2016 at 3:03 AM, Edward K. Ream wrote: Here, I'll write down my initial plan for a remarkable collapse in the > complexity of the code. > ​The start of the new code is at​ ​e9a78cb. The new code is disabled by the gen_v2 switch in basescanner.py. It will

ENB: Leo's line-oriented importers: the last collapse in complexity

I am writing this in the middle of the night, too excited to sleep. This is an Engineering Notebook post. Feel free to ignore. Here, I'll write down my initial plan for a remarkable collapse in the complexity of the code. I'll also record the genesis of this idea. I know from experience that

Quote of the week, thanks to dddddd on irc

https://lwn.net/Articles/704718/ Simulating these features in vim, Emacs or Eclipse is possible, just as it is possible to simulate Python in assembly language... — Edward K. Ream (Leo 5.4-b1 release announcement) -- You received this message because you