Thank you for the import script and the responses. I feel like maybe I'm missing something with @nosent though, why is it much harder to use?
Let's say I have a directory of files that are each templated, i.e. possibly having a header and footer. These files are checked into git and synchronized using @auto nodes and can both be edited and read _into_ Leo when changes occur, e.g. after git pulling. Then I can clone the body (inner section) of these nodes and write them out somewhere else using an @nosent file. Never would I want a change to this output file to be read back _into_ Leo. This file is local only and would not be checked into git, it could be deleted and would always be overwritten. As you know, Git prefers small files rather than large ones and this one could be quite massive and treated as a 'large file' and therefore lose certain functionality. Sure a script could do this too, but it's a poor man's version of using includes. Another issue I have is that this file is going to be quite _deep_ and html/markdown/asciidoc all have a maximum of 0+5 levels of section depth, so when *every* level of nodes writes as a section to the file then it breaks the output, so I need to be able to treat some nodes as sections and some as just body content. I've also decided that I can write my comments to file comments, so that Leo can write the whole subtree, even if i don't want to publish all of it. This large output file is only a temporary step because it would be transmuted before distribution and so asciidoc would exclude those comments. Kevin On Thursday, August 20, 2020 at 6:54:51 PM UTC-4 Edward K. Ream wrote: > On Thu, Aug 20, 2020 at 4:50 PM k-hen <[email protected]> wrote: > >> I'm feeling pretty stupid right now, I think this is what @asis & @nosent >> are for and I just missed it - even though I was staring right at it. >> > > No need for apologies! There is a lot to digest for newbies. > >> I've heard comments to avoid these and they're flagged as not >> 'recommended' and so was just dismissing them without consideration. >> I'm not sure if there are particular reasons *why* they're not >> recommended but I'll go ahead and give them a shot. >> > > I don't recommend @nosent or @asis because they are much harder to use > than @file, @clean and @auto. Leo's automagic reloading of @clean files is > what you want if you can't tolerate Leo's sentinels. If you *can* > tolerate Leo's sentinels, then @file is bullet-proof. > > I know from first-hand experience that getting @clean nodes to be as one > wants can take significant work when Leo's importers are up to snuff. I've > recently beefed up the C (C++) and typescript importers because importing > to @clean wasn't as easy as I would have wanted. > > 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3bf3fdc1-de5c-4728-82b6-246d86765094n%40googlegroups.com.
