Re: The future of Leo

2018-12-23 Thread Offray Vladimir Luna Cárdenas
Hi, I like the direction this is taking. I would like to have Leo bringing "outlining services" to other programs, including Emacs, Org Mode, Atom, Jupyter, Vim and/or Pharo. I imagine some kind of minimal test that allows external programs to connect to the "Leo Server" and use it from the

Re: The future of Leo

2018-12-23 Thread Edward K. Ream
On Sun, Dec 23, 2018 at 7:28 AM Terry Brown wrote: I'm not sure which parts of Leo you're talking about, but #1025 certainly > helps > on that front. Still not quite sure about the boundaries. > Boundaries are fluid, especially concerning Leo and org mode. I'll be writing about this in #1026.

Re: The future of Leo

2018-12-23 Thread Terry Brown
On Sun, 23 Dec 2018 05:53:15 -0800 (PST) "Edward K. Ream" wrote: > We can make Leo more accessible by integrating Leo's essentials into > emacs, vim, pyzo or even atom. I was going to say that I don't understand this project because I'm not sure which parts of Leo you're talking about, but

The future of Leo

2018-12-23 Thread Edward K. Ream
After Terry's recent announcement , it's a good time to consider Leo's future. See the summary. *Devs* Leo's devs remain a huge asset. Terry is still reading this group, and I will welcome his comments. Vitalije has proven