On Wed, Jul 16, 2014 at 9:00 AM, Kent Tenney <[email protected]> wrote:
> First impressions:
>
> - the @auto node icons indicate they are clones
Only if they are clones :-)
> - I'm not sure why the @persistence tree is visible, can it be used for
> something? Maybe somehow useful in resolving issues?
@persistence trees contain all data used to restore gnx's and uA's in
@auto nodes. So yes, they are used for something ;-) They are
visible because all Leo nodes are visible, but the recommended place
for them would be squirreled away in the @startup node.
I just upped code that starts to support @recovery trees in each
per-file @data tree:
1. pd.update_before_write_foreign_file now deletes all children of the
corresponding @data node *except* the first @recovery node (and its
subtree).
2. When an exact match for a unl isn't found, the read code calls
pd.recover_ua_for_gnx. At present, this does nothing, but it will
soon write a child of the @recovery node. Something like::
@recovered-ua <gnx> = <unl>
It's body text will be the pickled ua. This is, I think, about all
that can be done to preserve uA's when an url is not found.
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.
