On Fri, Jan 24, 2014 at 1:21 PM, Terry Brown <[email protected]>wrote:
> Hi Edward, twice now it seems your IRC connection has dropped just as I > was commenting on new auto, so I'll post here, you may have seen this. > Thanks for all these comments. First, rev. 6602 has new auto enabled on trunk, so people using bzr > might be testing it before you intended? > new_auto should always be False for now. Rev 6602 was a mistake that I corrected immediately, > > Also I said: > > 1) refresh from disk fails badly, doesn't insert @ignore and > corrupts outline, does comment that check failed in log > Thanks for this. I'll have to think how to support refresh from disk. > > 2) childless organizer nodes (i.e. comment nodes?) aren't > re-created, maybe they don't make sense anyway > Correct. They make no sense, especially in the present scheme, which inserts an organizer node when it first finds one of its descendants. Lacking any descendants, there is nothing to trigger its insertion. > > 3) maybe future development @views could restore v.u content > in @auto trees? > Excellent idea. It would be straightforward to do. > > which are all nits really, in general the handling of organizer nodes > in @auto looks very clever - I assume it does something similarly > clever with clones, but I don't usually use those, so am not sure what > to test. > Thanks. To test clone handling, just clone any node in an @auto tree and drag it *out* of the tree. The next time you reload the .leo file, the previously cloned nodes should still be clones. 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/groups/opt_out.
