Leo 6.8.6 contains support for `@leo`, including several supporting methods. This Engineering Notebook post discusses further improvements to Leo that will become part of Leo 6.8.7.
Background
`@leo` nodes help break huge Leo outlines into a top-level outline and sub-outlines. By default, there is one sub-outline for each direct subdirectory of a top-level directory.
The top-level outline (in the top-level directory) contains `@leo` nodes (links) to the sub- outlines. The sub-outlines contain:
- One `@leo` node (the back link) pointing to the top-level outline.
- One `@clean` node for each file (of given file types) in the subdirectory and all descendant directories.
It's easy to move between these outlines. Just select an `@leo` node and execute the `open-at-leo-file` command!
The challenge
`@leo` helps break up too-large outlines into more manageable sub-outlines. This performance improvement alone makes `@leo` invaluable. For the first time, it's possible to use Leo to study huge repositories.
But we Leonistas want to do more than just study repos! To contribute to large projects, we must also update our outlines after pulling large PRs from such large repos.
Surely, such automatic updates are possible. Leo's git-related commands provide a rough template. Aha! `@leo` nodes aren't just for us humans. Scripts will find them invaluable as well.
Summary
This post is pre-writing for documenting `@leo` for Leo 6.8.6. It is also pre-writing for a new enhancement issue for Leo 6.8.7.
`@leo` links help us Leonistas navigate between outlines. That much was always obvious.
But Aha! `@leo` links can help update scripts to find sub-outlines. I'll figure out how the update scripts will work a bit later :-)
Edward
Leo 6.8.6 contains support for `@leo`, including several supporting methods. This Engineering Notebook post discusses further improvements to Leo that will become part of Leo 6.8.7.
But we Leonistas want to do more than just study repos! To contribute to large projects, we must also update our outlines after pulling large PRs from such large repos.