On Wed, Dec 14, 2011 at 10:20 AM, HansBKK <[email protected]> wrote: > I've been trying to create "backup nodes" - copy-not-cloned parents > containing all the clones of an important @shadow file that has been > "flattened" in the past when updated externally, with a goal of trying to > preserve the outline structure, or at least assist me in rebuilding it if > necessary.
It's hard to comment on complex proposals such as yours. I am not likely ever to implement any such proposal, and certainly not this calendar year. The worst mistake I ever made with Leo was the notion of "backup" .leo files. It lead to impossible-to-predict data loss at arbitrarily long limes after the backup files were created. I am not likely to do anything similar ever again. I just came across a situation in which an @shadow tree got flattened. It happened because a unit test mistakenly deleted a private shadow file. Keeping this in mind, here are two different backup plans that you can do immediately, without changing Leo in any way: 1. Just copy the @shadow tree, and paste it elsewhere (perhaps in another .leo file), changing @shadow to @@shadow in the pasted location. This stores all info in the .leo file. 2. Make copies of the private files in the .leo_shadow directories. I have just verified that Leo's import-file command will indeed recover the information in .leo_shadow directories. Either way should safely preserve all the essential information. HTH. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. 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.
