It was a backup that first got me to realize the problem. Actually, it was a transfer to a new computer. All my files used to be on the C: drive and on the new one I used the D: drive. At the same time, I had thought I didn't need to transfer everything I had, because some of it was old anyway, or (I thought) could be reproduced from the Leo outlines.
Quite a while later, I opened up an outline and all the @clean files were blank. Eventually I realized that I needed to go through all of them and change the paths of the @clean nodes to the D: drive, and try to get the external files I could from the backups I had used to transfer everything. I didn't succeed for all of them, but at least got most of them back. My main use case, though, is that I need to produce some of my files clean - because they may have to be read, modified, or compiled by non-Leo users. It's the source control issue of controlling both the outline and the derived files that I'm mulling over. Of course, the easiest way is to source-control both, and maybe I'll start doing that. On Sunday, April 4, 2021 at 8:13:29 AM UTC-4 Edward K. Ream wrote: > On Sat, Apr 3, 2021 at 5:06 PM [email protected] <[email protected]> > wrote: > > I know of two ways to save clean files when their parent node is an >> *@file* node, both a little clumsy: >> > > I think keeping backups is the best way. Sure, Leo could have a > 'write-at-file-as-at-clean' command, but that would be featuritis, imo. > > 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/d71c0a1f-9f22-4798-b09d-09483335b5bfn%40googlegroups.com.
