On Monday, December 12, 2011 8:28:11 PM UTC+7, Terry wrote: > > > You can run this script to list all non-@<file> nodes in the log pane. > Thanks Terry I'll give it a shot.
> Reading over your importing projects ideas quickly they seem like they > > could work. For recognized languages (Python, C, Javascript, rst) you > can use the @auto import to get the initial structure into nodes, and > switch to @shadow after that, if you want. > > > No these are just text files, mostly "lightly" marked up with txt2tags, some asciidoc. I'd love to automate the breaking up into sections based on header format, but when I had a quick look at the "create a new importer" docs I got a bit intimidated. The "extract" command is very useful though. What I've found a bit frustrating is the fact that that one really does need to be careful about editing in Leo vs outside. When I kept getting "Recovered nodes" and "path changed" errors at one point I said OK, just delete the shadow folder and recreate it, but I ended up with a completely flat @shadow node - all its section children were deleted and the section << marks >> wiped! Fortunately I'd already clones all the section definition nodes over to my custom tree, so it was just a matter of reconstructing their order and copy/pasting the marks back in. I figure from now on I'll have an "external files backup" tree without any @ <file> directive, just plain text copy and paste of the section marks, off in a hidden corner of the leo file. And of course don't mess with the shadow folders 8-) I would have thought on re-reading @shadow nodes, if the leo file contains a conflicting information the Leo would prompt the user, or do a "Recovery node" like when the conflict goes the other way - it's obviously very cautious about the external files, but less so about the internal data. . . Of course it's likely the root cause is the nut behind the wheel, I've just started figuring Leo out. . . So far **such** a kewl tool! -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/WruOBOjaWgAJ. 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.
