On Monday, January 23, 2012 11:08:32 PM UTC+7, Differance wrote: > > > It seems to me that you're emulating what I'm recommending, only I have a > functional definition of the single clone @file -- it's for one unitary > external file, not any hybrid external file. If the distinction in > functions I'm describing were implemented, you'd have what you're trying to > do and it would be an aspect of the app that users would grasp based on the > difference in function. > Yes, and as I mentioned above, I'm 100% in favor of any Leo developments that help relatively inexperienced users to understand the issues and avoid the problems.
Sorry if the below seems nit-picky, but just I'm trying further our mutual understanding via clarifying terminology. I'm not sure about your "single" "unitary" qualifiers, since with all my projects, and most source code examples I've seen, one is usually dealing with a whole collection of files, often in a large hierarchy of folders. This is just as true for And perhaps rather than "hybrid" your "templating" term is equivalent (more commonly here "generated" or "derived")? As opposed to my "master source" idea, which I guess is somewhat like the VCS meaning of an "external branch"? The term "clone file" doesn't make sense to me, AFAIK it isn't ever safe to clone the actual @ <file> node, only its children. I don't know how you do things so you ensure Leo only imports from one of > those external files > Summary of my "SOP" - make sure that for any given node, only one clone instance is contained within an import-capable @ <file> directive (e.g. @file or @shadow) - all the rest must be export-only (@asis or @nosent). I haven't come across a way to ensure within Leo I'm not exporting changes to the "master source" branches - apparently there's a read-only plugin but I've only just found a reference to that, so far using my VCS has sufficed in practice. Alternatives or additional safety practices, paraphrasing from Ed, hopefully accurately: - only use <<sections>>+@others for the "master" @ <file> branch, use @all for the derived ones - make sure your "master" is the lowest @ <file> in the Leo file If the above is accurate, I believe it could serve as a starting point for a succinct summary to add to the official docs? Feedback of course most welcome. . . -- 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/-/xJ2cDO7jT-QJ. 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.
