Just starting with Leo, not a programmer, but have always been stimulated by brain-extension software like this, so far Leo looks like a life-changer. To put my feelings in context (and showing my age), I haven't been this excited since I saw Ray Ozzie demo Notes back in 1989. Before that was Ecco and Agenda, and after AskSam and not in the same league Evernote (v2 only please).
I only wish I'd discovered it earlier, I probably wouldn't have 50,000+ chunks and snippets locked up in a few dozen Evernote files 8- (. This has led me to desire full transparency and as much permanence in my primary content's storage - Leo's ability to let me keep the "content" data out as plaintext in a designated tree of my filesystem, while keeping krufty meta data out of the way in other parts of the filesystem - so kewl. OK, enough about me, on to my unreasonable wishlist request 8-) Please let me know if there's a way to accomplish this that I haven't found - I don't like the fact that the backlinks' tags, bookmarks etc are "hidden in the meta", I want to put these relationships if not in the content itself (not sentinels, I love @shadow) but perhaps in a delimited header/footer? Or at least in **my** meta-data text files I mentioned kept separate but somehow tied to the content files - parallel filesystem? So here's what I'm thinking for the moment - << section headings >>, while not actually *in* the body written out to the filesystem (can they be config'd to be automatically included?) are "close enough" that my workflow could include updating both at the same time. Based on that, I'd like a plugin (or something) that keeps track and ensures so that if/when I change the << section headers >> text in, it automatically does a search and replace throughout the whole shebang, keeping the other inline references in sync with the original target. Ideally this would operate on all @ <file> node types, even if they're not fully "loaded"? Although I concede a problem with @ <file> directives that aren't supposed to touch the external source, I think there should be a configurable setting to make this particular automated edit process an exception. I told you it was out there. . . I'm really hoping a response will start with "what you're asking for is completely unnecessary, because. . . " A less significant but related side question - one of my "master source" markup syntaxes is txt2tags, - yes it's too bad either that I hadn't chosen rest instead, or that Leo supported a pluggable choose-your-own-markdown-syntax architecture, depending on your POV, but I really prefer txt2tags' unobtrusiveness when working directly in the plaintext which has an %include operator as well as other pre/post operators for expansion macros, which I use for repeating text snippets, urls etc. I plan on tracking these in a distinct location in both my filesystem and Leo's tree to avoid confusion. Can anyone see systemic problems with this? I just can't see using cloning for such ittybitty chunks of text, would rather reserve them for the big-picture structural org functionality. Any sort of comments and advice greatly appreciated. . . -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
