Additionally, renaming a non-@<file> parent node will recursively set all @<file> child nodes to dirty. In my use of chapters this happens often. I will rename a chapter, or turn a node into a chapter and then all @<file> nodes under that (new) chapter will have to be saved because they've been set dirty. This seems unnecessary and avoidable.
The e is if the node being edited is an @path node. Obviously if a parent @path node is renamed then all @<file> child nodes should be set to dirty. On Tuesday, April 26, 2016 at 1:05:41 PM UTC-4, john lunzer wrote: > > Sorry, see my previous follow up post for correct details. > > On Tuesday, April 26, 2016 at 12:53:39 PM UTC-4, Edward K. Ream wrote: >> >> On Tue, Apr 26, 2016 at 10:17 AM, john lunzer <[email protected]> wrote: >> >>> Perhaps I should have been more specific. Marking is triggering a >>> recursive dirty setting regardless of node type. >>> >> >> Not in my tests. Can you give an example? >> >> 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.
