On Mon, Apr 25, 2016 at 4:33 PM, 'Terry Brown' via leo-editor < [email protected]> wrote:
> On Mon, 25 Apr 2016 13:16:08 -0700 (PDT) > john lunzer <[email protected]> wrote: > > > I think "dirty" is the right word, basically Leo thinks the file was > > altered. Not only does it do this for the current node but it will > > also do it recursively for all child nodes. > > Not sure if that's considered a bug or not. <enter><backspace> in the > body marks the node dirty too, Leo doesn't track edits that revert the > outline to an unchanged state. > > Quick test it seems that mark node / undo mark leaves things clean > (good), while <enter><undo> leaves them dirty, which is a > small nit. > A very small nit, if it exists at all. Outside an @<file> node, undoing a mark restores the previous changed state (shown in the tab) of the outline. Imo, there are no serious bugs here. EKR -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
