On Sun, Apr 27, 2014 at 4:41 PM, Kent Tenney <[email protected]> wrote: > I think the sharing discussion leans towards cart before horse, > first, get everyone using Leo.
I'm having trouble making sense of this comment. There will always be some who don't use Leo :-) > I'm most interested in discussions which involve enriching the > @auto experience; the ability of Leo to engage with a complex > set of files and add convenience and efficiency, asking nothing > of it's charges. That's certainly reasonable. @auto is my main way of studying other people's code. I typically convert to @file, thereby injecting sentinels, but that doesn't matter because I never push the changed code. Improvements in @auto really speed the initial conversion to @file, which can be a major convenience. > Along these lines, I think persistent UAs for nodes in @auto files would > be keen. If the parsed tree of a py file was unchanged since the > last time it was loaded, the UA for a node would contain state from > before. I'd put timestamps in there, but others might have more > interesting ideas. If the source file is slowly changing @shadow already does what you want. The private files contain sentinels, so you get everything @file gives you, including gnx's, clone links and uA's. In short, improving @auto and @shadow will always pay dividends. This is, in fact, the real take-away message from this entire thread! HTH. 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.
