Hi Ed et al, Sorry to be resuming my presence with a bug report, but here goes.
Leo is destroying data! :( What happens is: 1) I create and populate a @file node, then save the Leo file and quit Leo 2) At a later time, I restart Leo and load the project Leo file 3) The @file node refuses to load, and I get the following message in the log pane: reading: /home/david/code.leo reading: @file main.php ----- read error. line: 5, file: main.php bad tnodeList index: 1, <vnode 153631820:'@file main.php'> At this time, if I save the Leo file I'm screwed. The former contents of the @file node are headed for Disneyland. Workaround is to watch for similar error messages on loading the Leo file. For each @file that Leo fails to load, delete the @file node from the tree, then do an 'import derived file'. This doesn't work properly, since all child nodes sit just underneath the parent, and not in the correct hierarchy. But it's better than losing the data. Another workaround is to just use @nosent nodes, and only switch to @file nodes temporarily if necessary. This is a somewhat dangerous bug, to say the least. Considerable data loss risk. Any ideas, Ed? Cheers David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
