Over the last year or so, I have used @auto-x more and more (in particular, @auto-md) because I like the 'clean' external files that replicate the organization of the nodes in Leo. However, more recently as I began relying on tagging, back links and clones, I am running into major limitations with @auto-x (and to a lesser extent with @clean). (See also the recent post on uA storage.)
What would be really beneficial would be a 'hybrid' @<file> type that writes and maintains org structure (node headline text) in the external file based on @language (md, org-mode, rst, etc.) while also utilizing the tagging, linking and cloning features of Leo. As I see it (please correct me if this assumptions are wrong): - @file maintains all of the Leo features described, but the external file includes sentinels. - @clean keeps uA information (tags, links, etc), but loses cloning information. Also, @clean *does not* write node headline text to external files. - @auto-x loses both uA and cloning information, but *does* write node headline text into external files (based on type). Thoughts or ideas? Rob.......... -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
