Shrinking pane contents

Recently I switched from using my desktop and a mouse to using my laptop with a touchpad. Much too often the contents of a Leo-Editor pane suddenly shrinks or expands. Usually the text in the body pane shrinks to so tiny that the whole pane contents are just a few dots. When this happens

Re: Atom might be Leo's future

On Wed, Feb 21, 2018 at 1:35 AM, Edward K. Ream wrote: > On Tuesday, February 20, 2018 at 10:17:52 AM UTC-6, Zoom.Quiet wrote: > > Thanks for these comments. It's good to know that Atom may not perfect. > Hehe. > > > ... has a large user... <-- that is maybe hallucination

Re: A Recent Article by Me

This is awesome. I really think the following paragraph from your article summarizes the unparalleled utility of Leo. Outliners impose structure on documents. Sadly, they can also impose structure on our thinking, making creativity a lot harder. Leo is different. Instead of imposing structure,

Re: ENB: Adding Leo to Atom

ENB <-- means ? On Wed, Feb 21, 2018 at 2:32 AM, Edward K. Ream wrote: > This is blue sky thinking. Nothing is certain. > > The goal: *turn Atom into Leo in the simplest way possible*. > > The simplest thing that could possibly work might be to loosely base the > leo plugin

Re: Atom might be Leo's future

​ ​​ On Tue, Feb 20, 2018 at 9:52 AM, Edward K. Ream wrote: ​> ​ Don't panic. Note the word "might" in the title. ​The process of "living with what I wrote" has *increased* my doubts about using atom or vscode. See below. ​ ​> Afaik, atom does everything it has *in

Re: Atom might be Leo's future

On Tue, Feb 20, 2018 at 11:00 PM, Xavier G. Domingo (xgid) < xgdomi...@gmail.com> wrote: > Wow, this is amazing! I had this exact same idea about two weeks ago, but > for taking the best of Leo to VSCode instead of Atom! > ​Many thanks, Xavier, for this. I did not know anything about VSCode

Re: ENB: Adding Leo to Atom

On Tue, Feb 20, 2018 at 8:15 PM, Zoom.Quiet wrote: > > >> - Opening a .leo file (in atom) will init *python state data* in the >> python kernel. *Python code* in the kernel will load the .leo file and >> create a representation (a tree of vnodes, or an sqlite db) of the

Re: A Recent Article by Me

On Tue, Feb 20, 2018 at 5:40 PM, Satish Goda wrote: > This is awesome. I really think the following paragraph from your article > summarizes the unparalleled utility of Leo. > > Outliners impose structure on documents. Sadly, they can also impose > structure on our

Re: Atom might be Leo's future

Wow, this is amazing! I had this exact same idea about two weeks ago, but for taking the best of Leo to VSCode instead of Atom! I've recently re-discovered VSCode thanks to a plugin made by a colleague at work and I'm nearly falling in love with it. Clean interface, quite fast (you have to try

Re: Atom might be Leo's future

Regarding performance, VSCode is beating Atom by far according to Atom users themselves: https://github.com/atom/atom/issues/10188 On Wednesday, February 21, 2018 at 2:00:47 AM UTC-3, Xavier G. Domingo (xgid) wrote: > > Wow, this is amazing! I had this exact same idea about two weeks ago, but

Re: effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

On Tue, Feb 20, 2018 at 12:45 AM, Edward K. Ream wrote: > On Mon, Feb 19, 2018 at 9:33 AM, Zoom.Quiet wrote: >> after test, i confirm: >> >> - change @rst -> @clean, will lost so many rST need support by Leo >> - and @rst really can not auto merge

Atom might be Leo's future

Don't panic. Note the word "might" in the title. Before going further, please look at the Why Atom? page. It would also be good to install atom and read

Re: Atom might be Leo's future

On Tue, Feb 20, 2018 at 11:52 PM, Edward K. Ream wrote: > Don't panic. Note the word "might" in the title. > > Before going further, please look at the Why Atom? > page. > It would also be good to install

Re: Atom might be Leo's future

On Tuesday, February 20, 2018 at 10:17:52 AM UTC-6, Zoom.Quiet wrote: Thanks for these comments. It's good to know that Atom may not perfect. Hehe. > ... has a large user... <-- that is maybe hallucination ;-) Is there any reason you say this? > VSCode base same construct with Atom... > -

ENB: Adding Leo to Atom

This is blue sky thinking. Nothing is certain. The goal: *turn Atom into Leo in the simplest way possible*. The simplest thing that could possibly work might be to loosely base the leo plugin on the existing hydrogen plugin . Please enable the hydrogen

Re: Atom might be Leo's future

On 2/20/18 11:17 AM, Zoom.Quiet wrote: On Tue, Feb 20, 2018 at 11:52 PM, Edward K. Ream > wrote: Don't panic.  Note the word "might" in the title. Before going further, please look at the Why Atom?