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.
Is there some documentation somewhere describing how to move a Leo file and what it generates? I know I'm not using the right names for things but I'm still haven't fully internalized the Leo nomenclature. On Tuesday, May 16, 2017 at 11:27:56 AM UTC-4, Eric S. Johansson wrote: > > I just went to look in one of my Leo files and I just found that I've lost > all of my content under the@file nodes. The only hint I have is: > > restoreDescendantAttributes: can not find VNode (expanded): gnx = > alsoeric.20170209115147.1, tref: alsoeric.20170209115147.1 > > I don't know if this is related or a red herring. The files I lost the > content of were an original and a duplicate. I remember working with a > duplicate and it seemed to be okay but now it's data is also lost. > > I'm rooting through my backups now to try and recover the original file. > I'll let folks know what I find when I find it > I think I've seen something like this when I forget to save a Leo file. > I'm going to go look through my backups and hopefully be able to recover. > > -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
