Wondering about current status and potential direction: There have been a couple of mentions of @auto nodes gaining persistence, what are the chances of this happening in core? Something like persistent UAs, such that @auto <file.py> would store the UAs of the tree, putting them in it's UA.
I'll start on scaffolding outside Leo to persist @auto nodes if this isn't going to happen, but core would be nice. #cough#(someone else does the work)#cough# I think there would be potential benefits beyond my particular proclivities. No other tool offers the power of transparently bringing the power of a database to code in this way. There is also a pretty old bug in 'refresh from disk' just saying ... https://groups.google.com/forum/#!topic/leo-editor/Qp4D74Ig_jY https://bugs.launchpad.net/leo-editor/+bug/1259127 Thanks, Kent PS I've realized another reason @file doesn't interest me other than the problem with sentinels when editing outside Leo. I place a lot of value on structuring with Leo, the huge benefit of hierarchical arrangement of headline/body pairs. Content that lives in the Leo file gains value through the power of outlining. However, when working with source code, I consider the correct structure to be that provided by the language: declarations, functions, classes, methods ... exactly what @auto does, no more, no less. Of course this is a matter of taste, not correctness. -- 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.
