On Jan 24, 6:24 am, "Edward K. Ream" <[email protected]> wrote:
> I just found, presumably, the cause of the bug just reported that new > nodes remain dirty after a save. There seems to have been an > "unforced error" in c.setChanged. Fixed on the trunk at rev 2753. I see why I made the mistake. The old code special-cased @file and @noref nodes, and I mistakenly thought the code applied *only* to those kinds of nodes. In fact, the code applies to all nodes *except* those nodes. 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.
