Hi, How does one SAFELY move a .leo file with many @file nodes to a different path? I have something like:
- Stuff @path K:\code - @file later\foobar.py - @file after\foobar.py - @file soon\barfoo.py and need to move it to @path D:\New_code. I tried recursively copying the directory tree to the new location (well, actually unpacking from a zip file. The old path is no longer available.) but when I open Workbook.leo all of the file nodes are empty, because it can't read from K:. I tried changing the top @path, saving, exit and restart Leo, but all of the @file nodes remain empty. I tried editing the .leo file in an external editor and changing the path there, but that didn't help. Selecting the top @path node "r-click > Path > Update recursive" also did not restore the missing file node contents. Looking at the files on disk I discover that every single one of them has been zeroed out! I've been working on this project for months and this is a major loss. All of the @files are stored in a code repository (mecurial) so the critical data can be restored. However there's a lot of information in the Leo file too vis-avis their relationships to each other, clones, and so on. As per the recommended way of working with SCMs the .Leo file itself is not under version control. This seems an *extremely* fragile setup to me and I'm very disconcerted. And concerned about the future of Leo. What if I'd not been using version control at all?? -- -matt -- 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.
