On May 17, 9:53 am, "Edward K. Ream" <[email protected]> wrote:
Here is excerpts from Steve's reply: QQQQQ > 1. A set of additions to Leo, with a strong bridge between Leo and > vim. Perhaps something like the leoBridge module could be made part > of vim. Maybe. Right now, standing on one foot, I'd imagine the main bridge would be conversions Leo->VimOutliner and VimOutliner->Leo. Plus possible support for some of the most common VimOutliner keystrokes, although you already mentioned your disinterest in modal editing. > 2. A set of additions to vim, written in vim's scripting language that > emulate key parts of Leo. Doubtful. If we wanted a Vim engine, we'd keep adding features to VimOutliner. We've added just about every VimOutliner feature we can using Vim as the engine. > 3. Support, in vim's core, for Python. Leo's features could then be > copied and pasted from Leo to vim. Probably not -- same reason as #2 > Any of these ways, or any other way, would be fine with me. > > If clones are important to you, the big question is whether you will > find a way to do without sentinels containing gnx's. Clones will be an important part of the new program -- we've been trying unsuccessfully to add clones to VimOutliner for a decade. The second clause of your preceding sentence went right over my head -- I don't know what sentenels or gnx's are. QQQQQ Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
