I would like the facility to flag a given node in order to disable editing it from within Leo, but still leave it receptive to reading incoming changes from the filesystem. These are generally within @shadow trees.
Is there such a beast? Not requesting that there be, just inquiring. I imagine that making such a facility recursive, applying to the nodes below, would cause further clone-war-style problems. ==================== Sidetrack on @ignore - probably mostly off-topic to the above I had thought from reading this http://groups.google.com/group/leo-editor/browse_thread/thread/bac65cb75484f7cb?pli=1 that I could use @ignore to prevent my edits within Leo from being written out to the filesystem, but seeing that's 3+ years old, and having found little other doc guidance on explicitly **using** @ignore for content nodes (as to opposed settings, or leo automatic use of them for data loss prevention) and having found many explicit statements along the lines of: "@ignore is forbidden in any @file trees" ( - including @shadow? - all @ <file> type directives? ) I have decided to ignore @ignore for the moment. . . -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/-MDUVHj8vtUJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
