Re: My 15 year plan, part 2

2016-09-17 Thread Edward K. Ream
On Sat, Sep 17, 2016 at 7:06 AM, Kent Tenney wrote: > Sorry, neovim is a C rewrite, pyvim is the Python vim > https://github.com/jonathanslenders/pyvim > ​I'll look at it. However, integrating it into Leo is not likely to be easy because it uses prompt_toolkit

Re: My 15 year plan, part 2

2016-09-17 Thread Viktor Ransmayr
Hello Edward, On Sat, Sep 17, 2016 at 11:33 AM, Edward K. Ream wrote: > On Thu, Sep 15, 2016 at 3:45 PM, Kent Tenney wrote: > ... > > ​ > ​> ​ > However, foolproof install seems to be job one. > ​We will have to disagree about this one. Leo has a quick

Re: My 15 year plan, part 2

2016-09-17 Thread Kent Tenney
Sorry, neovim is a C rewrite, pyvim is the Python vim https://github.com/jonathanslenders/pyvim First impressions count, but I'm no packaging expert either ... On Sat, Sep 17, 2016 at 4:33 AM, Edward K. Ream wrote: > > > On Thu, Sep 15, 2016 at 3:45 PM, Kent Tenney

Re: My 15 year plan, part 2

2016-09-17 Thread Edward K. Ream
On Thu, Sep 15, 2016 at 3:45 PM, Kent Tenney wrote: > Neovim is a Vim rewrite in Python > ​. > ​I see only C files at the neovim github repo . Why do you think neovim has python sources? ​ ​> ​ However, foolproof install

Re: My 15 year plan, part 2

2016-09-15 Thread Kent Tenney
I don't see Leo-in-thing, I see Thing-in-Leo. Leo's panes, buttons, scriptiing external file tools, plugins etc. provides the fundamentals which make it uniquely positioned as a cognitive aid. Neovim is a Vim rewrite in Python, if it could be native to a Leo editor pane, the Vim/Leo choice would