Re: FYI: Embedding Leo in pyzo, emacs or vim

Spyder seems an interesting option also. This part called my attention: > Spyder can also be used as a PyQt5 extension library, allowing developers to build upon its functionality and embed its components, such as the interactive console, in their own PyQt software. So, maybe is easier to call

discussing: Leo unique and essential features #1025

Thanks for this - https://github.com/leo-editor/leo-editor/issues/1025 On first read something that struck me as missing from discussion of a defining feature is the concept of nodes, closely followed by their easy move-ability. One could argue this is wrapped in the over-arching concept of

Re: FYI: Embedding Leo in pyzo, emacs or vim

Of the 3 Pyzo is most interesting to me personally because it's a tool I use and keep coming back to. The ability to switch python versions and environments with restarting is gold. This is purely a user-side preference, with zero idea of how pyzo integration might help Leo or how difficult it

Re: Moving on from Leo

Terry, When I chanced here it was your warmth and helpful responses to my at-times-idiotic newbie questions that first encouraged me to stick around long enough to find personal engagement with the Leo project and community. To my amazement it's to the point that I've now made a couple marks

Re: FYI: Embedding Leo in pyzo, emacs or vim

On Wed, Dec 26, 2018 at 7:35 AM Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > I think that the host editor for Leo should have something like a place to put the document outline...That's why I was thinking that OrgMode could be a first interesting experiment. It's an open question

Re: FYI: Embedding Leo in pyzo, emacs or vim

On 25/12/18 13:10, Edward K. Ream wrote: > > > On Monday, December 24, 2018 at 10:08:13 AM UTC-8, Edward K. Ream wrote: > > > ...embedding Leo in pyzo might be both the > easiest of the three projects. > > Hmm.  There seems to be no official way of extending pyzo, so it's >