Because you can never have too many @file flavors ;-) I'll point out there's a plugin that adds a @text node which maybe does closer to what Kent was expecting. When you double click on something it reads the file, writes the file on outline save, I think.
On Fri, 20 Jun 2008 09:03:35 -0700 (PDT) "Edward K. Ream" <[EMAIL PROTECTED]> wrote: > > On Jun 20, 9:04 am, "Kent Tenney" <[EMAIL PROTECTED]> wrote: > > > Why would Leo look for sentinels in the disk file when > > encountering a @nosent node? By definition there are no > > sentinels, so I'd expect the lack of them to be expected by Leo. > > Kent, you are confused. Leo isn't looking for sentinels, but Leo > can't read the @nosent outline without them. Thus, Leo *can not* read > the @nosent file: all the info must be in the outline. > > What you are expecting, I suppose, is for @nosent to be equivalent to > @auto. But they are very different. With @nosent, *you* can organize > the outline as you like. With @auto, you get exactly what the import > code gives you, and no more. > > Anyway, the trunk contains logic for @nosent similar to @auto. Leo > will not write an @nosent node if it contains less than 10 characters > and has no descendants. This should prevent unwanted writes. > > Edward > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
