Triggered data loss in Leo

[Eric S. Johansson]

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. 

[Eric S. Johansson]

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.

[Edward K. Ream]

On Tue, May 16, 2017 at 11:16 AM, Eric S. Johansson <ynotla...@gmail.com> 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 near the top of the Directives Reference 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

[123 456]

yes I did recover from my backup. I was sweating bullets there for a bit. :-)

> --
> You received this message because you are subscribed to a topic in the
> Google Groups "leo-editor" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/leo-editor/QjtdMgqV-eQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> leo-editor+...@googlegroups.com.
> To post to this group, send email to leo-e...@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.

[Edward K. Ream]

On Wed, May 17, 2017 at 1:02 PM, 123 456 <ynotla...@gmail.com> wrote:

yes I did recover from my backup.  I was sweating bullets there for a bit. :-)

​Glad to hear it.

Edward