On Sun, Jul 27, 2025 at 7:24 AM Edward K. Ream wrote: 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. > Still true, but Leo's present code probably *already* suffices to handle updates in large repos! I had forgotten the recent improvements to @clean! Indeed, @bool report-changed-at-clean-nodes = True enables the following cool features: - Leo makes clones of all changed nodes and organizes them in the last top-level node. - Leo calls the appropriate importer on the text of each changed node. This should ensure that Leo gives each added function or method its own node! Note that the update algorithm will automatically delete nodes as necessary. *Possible improvements* Ah, the joys of documentation. As I write this, I see two improvements are possible. 1. Leo should re-import changed nodes even if the setting above is False. 2. The c.makeLinkLeoFiles script helper (See PR #4395 <https://github.com/leo-editor/leo-editor/pull/4395>) should contain a kwarg that gives the value to assign to @bool report-changed-at-clean-nodes This setting becomes crucial for large repos! *Summary* I'll create a new PR for improvement 1, and add improvement 2 to PR #4395. These tweaks should not affect the release date of Leo 6.8.6. I welcome all comments and suggestions. There is plenty of time for debate. 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 email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0KAgSjPeEmceQMLz82DheZqgzVckereSKQy5pSuK%2BpuA%40mail.gmail.com.
