On Saturday, June 24, 2017 at 10:20:04 AM UTC-5, Edward K. Ream wrote: > > The *acid test* for switching branches is to ensure that after switching branches it's possible to do write-at-file-nodes on the top-level Code node without changing any external file.
> This test now passes. Still true ;-) I'm starting to wonder whether recovered nodes are *ever *a good idea, even in the "rare" case where two different external files defined the same node (gnx) differently. Indeed, the simplest thing that could possible work is to scrap *all* the recovered nodes logic, including all the new_read logic. This is feasible: external files will always override data from clones appearing in the .leo file. Because the "rare" case will, in fact, be rare, we could simply let git tell us when nodes change unexpected. That would be easier if #501: Create outline-oriented git diff <https://github.com/leo-editor/leo-editor/issues/501> were in place. So *maybe* I'll complete #505 by drastically simplifying Leo's read logic, and turn my attention to #505. However, before I can do that I have to understand why the the node comparison code seems never to be called. #505 requires a lot of patience... Edward <https://github.com/leo-editor/leo-editor/issues/501> -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
