Trying another approach - first clarify my case, more general that the "backup trees" discussed above:
A - "master" tree - imported from external source files, **should** never be updated within Leo, as I break it down into chunks with sections/@others, I constantly write the files back out using @shadow and diff against the checkout to ensure my Leonized representation continues to output exact matches with the original files. B - "custom" trees - a re-factored mix of cloned nodes from A and original content. If necessary can set as SOP that the custom nodes are **only** edited within Leo - obviously the contents of the cloned-from-A ones aren't touched at all. The B trees do need to be "published" back out to the filesystem, but I've found that using @shadow here results in entire trees's worth of nodes getting destroyed, either flattening everything into the parent body, sometimes leaving content only out in the filesystem. Restricting the B tree's @ <file> nodes to @all - the approach recommended two years ago, waiting confirmation if still applies > My suggested rule is this: when putting clones in external files, make > sure the clone appears in at most one external file that does not contain > an @all directive. > doesn't give me the flexibility of control I'd like, although if this really is the only safe way. . . One alternative I'm now looking at is using @nosent directives for the B tree, thus enable **one-way out-only publishing** from Leo, along with the SOP mentioned above, realizing that I can't edit content via the external files, only from within Leo. Questions - Do you think this approach is safe? Any cautions to add to the SOP? - Any thoughts on an alternative path? If this works, then it should handle the "backup trees" being written out to the filesystem as well. -- 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/-/lrpv_WE7nH4J. 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.
