On Tue, May 16, 2017 at 11:16 AM, Eric S. Johansson <[email protected]> wrote:
Okay, I think I figured it out. I rearranged and "cleaned up" my working > directory before I did my initial check into git. I want to get rid of my > prototype code and make it more production-ish. What I didn't realize was > that the.Leo file doesn't actually contain the nodes/sections all the time. > Yikes. Git can't help you if you never check files in. I do hope you were able to find backups. Is there some documentation somewhere describing how to move a Leo file and > what it generates? > Not for exactly this topic. This table <http://leoeditor.com/directives.html#part-1-file-directives> near the top of the Directives Reference <http://leoeditor.com/directives.html> lists the differences between the various kinds of @<file> directives. @clean, @shadow and @file require their corresponding external files. @shadow also requires the contents of the "shadow" subdirectory. If you want the .leo to be self contained, you can use @nosent, but then you lose the ability to update the outline based when the external file changes. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
