On Fri, Feb 13, 2015 at 6:33 AM, Kent Tenney <kten...@gmail.com> wrote:
import issues aside, I see @nosent as @auto which keeps a > copy of the external file in the Leo file, persisting gnx and ua. > Yes. The only reason I can think of to prefer @auto is if the Leo > file was dealing with so many external files that size became > an issue. > Good point. However, reading even large .leo (xml) files is fast: the slow part is opening all the external files. Would @edit be the choice for managing external files while > keeping the Leo file minimal? > Yes, it's an alternative. Compared to @auto, each change in an external file triggers > a git diff in both the Leo file and the external file ... that's fine. > I agree. Drat. I truly believe that @auto should go, but now it's not a no-brainer. Instead of *all* gain and no pain, the .leo file expands. But still, the drawbacks of @auto are *huge* compared with the new @nosent. Indeed, if we had had the new @nosent from the beginning nobody would have thought of using @auto. And I absolutely detest the fact that the root node of @auto-org, etc. doesn't contribute to the output. I don't see how we can retain @auto without also retaining @auto-org, @auto-rst and @auto-vimoutline. So, unless I hear howls of protest, all forms of @auto are still on the chopping block. There is *no* doubt that killing @auto will greatly simplify Leo for newbies. Thanks again, Kent, for your comments. It's very important to think through all the implications... 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
