On Sunday, March 8, 2015 at 8:22:27 PM UTC-5, Steve Zatz wrote: > ...I just want to provide my own thoughts about the importance of @clean.
> There have been some posts about the recovered nodes, comparing the old and new nodes where there were external changes. I think it's genius. After spending three days deep in the code's innards, I have just realized (and verified) that @clean will do a *much* better job reporting recovered nodes than will @file (or anything else). This is something that has been hidden in plain sight! Leo stores all nodes of the @clean tree in the outline. For any node in the @clean tree, it's easy to compare the old body text (from the outline) with the new body text, the value computed from the update algorithm. As a result, Leo can warn when *any* node in an @clean tree has been changed outside Leo. In contrast, the only nodes in an @file tree that Leo stores in the outline are clones appearing outside all other @<file> trees. I use clones a lot, so Leo can often warn about recovered nodes, but you could call those warnings accidental! In short, storing all nodes of an @clean tree in the Leo outline has an important, unexpected benefit. 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.
