On Thu, 29 Jul 2010 09:27:06 -0500 "Edward K. Ream" <[email protected]> wrote:
> Hmm. This might be a boundary case. When using new sentinels, there > are no @nonl or @nl sentinels. The effect is intended to guarantee > that nodes always contain a trailing newline when Leo reads them. But > it's possible that some situations don't yield that. > > Please send me an example when this happens to you. It's not something that's happening on read, but when I'm creating code I seem to be seeing more cases where a node I just created generates a syntax error on write because it doesn't contain a trailing newline (or more proximally because the file the writing process writes doesn't contain a newline between the content of the node and the next node, so `returndef next(self):`. Cheers -Terry -- 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.
