This commit happened Wednesday, October 22, 2014 6:08:06 PM Since then, a botch in ni.getNewIndex caused copying and pasting an outline to assign the same gnxs to all the vnodes in the pasted tree. This is a terrible bug, one that can easily cause data loss.
Here is what you may have seen: you copied and pasted an outline, and all appears well: the pasted outline appears to be completely different from the original outline. But when you reload Leo, all the nodes in the pasted outline are clones of the original nodes! Danger! Before saving any such bizarre file, get the latest copy of Leo, make a backup copy of the .leo file, reload the .leo file, delete the copied outline that has now turned into clones and save the file. This *might* restore things as they were before the copy/paste, but there are no guarantees. My apologies for this blunder. There are now permanent checks in the paste-outline code that will complain if this kind of thing happens. It's like an always-active unit test. As you can see from the git log, this bug wiped out some notes in leoNotes.txt. No problem with git! After fixing the bug, I just reversed the hunks that deleted the text and reloaded Leo. This would never have been possible in bzr. I do hope you all use git for all your work... 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
