On Tuesday, February 14, 2012 4:18:56 AM UTC+7, Matt Wilkie wrote: > > > but I really don't see any other way of doing it.
My "SOP as workaround" solution would be to: - Keep the code for your batch in a sub that can get cloned, don't clone the @ <file> node directly. - In the location that writes to your VCS, make the parent a @file or @shadow, whatever two-way-writing directive you usually use. - In the location(s) where you want a file to be output-only, make the parent(s) @nosent - Remember not to try editing the batch file out in the filesystem, it must be edited either in Leo, or in the file under VCS. Ed has spec'd other schemes (outlined above) taking advantage of relative priority based on vertical location in the .leo file, or alternatively on the relative priority of @all vs <sections>+@others. -- 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/-/3Yef7oQyoEkJ. 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.
