Rev 419a82d changes several aspects of how Leo handles the so-called orphan
bit in vnodes. These are major changes, but I believe they will be for the
best.
The orphan bit indicates that there was a problem writing an @<file> node.
It will be set, for example, when an @file node contains children but has
no @others directive. Leo simply cannot write the external file in that
case.
However, Leo went overboard with the error logic. Here are the recent
changes:
1. Leo no longer writes the orphan bit ('O' bit in vnode attr) in .leo
files. This kind of persistent error bit seems unwise.
2. Leo clears the bit and issues a warning when reading a vnode with the
'O' attr.
Previously, Leo would refuse to update the outline from the external file
if the orphan bit was set! This makes no sense because Leo never writes
erroneous external files! Why should Leo consider such files to be
dangerous?
This change could have unforeseen consequences, but I suspect nobody will
ever notice. The foreseen consequence is that Leo will keep the outline
and external files in synch more often.
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.
