Finished reading through the documentation for g.findRootsWithPredicate.
That helps with what I'm looking for!
It's a still bit daunting reading through the Leo documentation, but I
think I'm getting used to it. I found it's easier to Ctrl+F through the Leo
doc files inside of Leo.
On
todo.py works as expected, so I can think of no reason not to do the merge.
Please report any problems immediately.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an
On Thu, Aug 23, 2018 at 6:00 AM Edward K. Ream wrote:
*A proposed new principle*
>
> Suppose that *each command is responsible for setting focus*.
>
This plan did not survive the first contact with the code. There are way
too many calls to mess with. I do not plan a separate "focus" branch.
I
On Thu, Aug 23, 2018 at 6:02 AM john lunzer wrote:
I've seen scathing accusations of other codebases as well. I've seen Vim's
> codebase regarded poorly, as is Vim's scripting language. I've seen
> articles belying the complexity of Netbeans' codebase. Elisp (on which much
> of emacs is written)
I've seen scathing accusations of other codebases as well. I've seen Vim's
codebase regarded poorly, as is Vim's scripting language. I've seen
articles belying the complexity of Netbeans' codebase. Elisp (on which much
of emacs is written) is often referred to as "terrible" or "horrible",
This is an Engineering Notebook post about focus-related issues. It will be
of interest mostly to Leo's core devs. Feel free to ignore.
This will be pre-writing for a possible new enhancement issue relating to
improving Leo's focus-setting code. Any new code will appear in the
"focus"
