On Wednesday, June 14, 2023 at 11:06:01 AM UTC-4 Edward K. Ream wrote: On Wed, Jun 14, 2023 at 8:06 AM Edward K. Ream <edre...@gmail.com> wrote:
On Wednesday, June 14, 2023 at 8:00:08 AM UTC-5 Edward K. Ream wrote: PR #3363 <https://github.com/leo-editor/leo-editor/pull/3363> improves the outlines created by scripts that call c.recursiveImport. One more thing: leo-editor-contrib <https://github.com/leo-editor/leo-editor-contrib> contains an improved mypy.leo <https://github.com/leo-editor/leo-editor-contrib/blob/master/StudyOutlines/mypy.leo> that illustrates the new import scheme. And one more thing. Imo it would be best to replace the @path statements in headlines with @path statements in body text: @path statements are context sensitive. That is, they "accumulate". But this means that cloning and moving an @<file> node will change its effective path. Yes, pluses and minuses. With an @path node in the headline, it's instantly clear where all the external child files are located. If the @path directive were in the body, this wouldn't be so. But the point about clones is an issue too. Another matter is how much code is out there that looks for @path in the headline. I don't know, but we should probably assume there there is some user code that's not part of the Leo source tree. -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/95f2683b-d419-4319-bc14-556b89483e27n%40googlegroups.com.
