On Jan 7, 5:13 am, "Edward K. Ream" <[email protected]> wrote:
> > Now if one exits Leo, adds a single space in every line in the public > > file, and re-opens Leo, the error is:... > > unexpected @nonl directive in code part This example really stresses the update algorithm. It's a fascinating test case. It's relatively easy to get rid of the error, but the result is that all the changed lines get sucked into the top-level node: the child node gets denuded of all its text. Also, the error recovery after the (essentially fatal) read error is poor: *all* the text goes away. This probably can't be helped, so it's essential not to take a read error :-) More to come when I know more... Edward
-- 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.
