Re: Félix: would Position/Vnode methods in ts be a good idea?

On Wed, Aug 5, 2020 at 3:09 PM Félix wrote: > although sending the whole tree structure after calls have been resolved > (when idle) to remove the need to call the python side when only browsing > without changing the structure, would be an improvement in speed (for > future improvements after ma

Re: Unintuitive user interface

On Wed, Aug 5, 2020 at 3:14 PM Félix wrote: > Ah! So it should be understood/named as "promote children" (its children > become siblings) and "demote siblings" (siblings become its children) > Exactly. Edward -- You received this message because you are subscribed to the Google Groups "leo-e

Re: Unintuitive user interface

On Wed, Aug 5, 2020 at 3:24 PM Félix wrote: > those 2 have thrown me off for years so i'm thinking of adding the > "children/siblings" suffixes to the commands in leoInteg ;) > This is a perfectly reasonable thing to do in vs-code, because it's so easy to find commands using the command palette.

Re: Unintuitive user interface

On Tuesday, August 4, 2020 at 5:55:25 PM UTC-5, Félix wrote: > No other editor uses ctrl+u, d, l or r. But on the other hand, i dont know of any other outline editor 😄 As an historical note, the MORE outliner , on which Leo is based, used these

Good news re leoAst.py

In a previous thread I said that work on this project is complete. However, I have some news to report. Guido and I have been discussing whether it makes sense to add the capabilities of leoAst.py to python's stdlib. We both now agree that doing so would be a bad idea. To summarize: adding even

Re: Unintuitive user interface

On Thursday, August 6, 2020 at 7:05:11 AM UTC-4, Edward K. Ream wrote: > > On Tuesday, August 4, 2020 at 5:55:25 PM UTC-5, Félix wrote: > > > No other editor uses ctrl+u, d, l or r. But on the other hand, i dont > know of any other outline editor 😄 > > As an historical note, the MORE outliner >

Wanted: a future maintainer for leoAst.py

There is only one drawback to not having leoAst.py be part of python's stdlib. The python devs will never be responsible for updating leoAst.py when python adds new kinds of ast nodes. New ast nodes are sometimes required to support new language featu