Re: solution: clearDirty @ nodes when working with chapters/organizational nodes

2017-03-06 Thread Edward K. Ream
On Mon, Mar 6, 2017 at 10:37 AM, john lunzer wrote: > I have commit access, I'll see if I can make some time this week(end). > ​Great. Thanks! Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

Re: solution: clearDirty @ nodes when working with chapters/organizational nodes

2017-03-06 Thread john lunzer
I have commit access, I'll see if I can make some time this week(end). On Monday, March 6, 2017 at 7:29:21 AM UTC-5, Edward K. Ream wrote: > > On Sun, Mar 5, 2017 at 2:24 PM, john lunzer > wrote: > > After using these for a few days I think mark-node-clean and >>

Re: solution: clearDirty @ nodes when working with chapters/organizational nodes

2017-03-06 Thread Edward K. Ream
On Sun, Mar 5, 2017 at 2:24 PM, john lunzer wrote: After using these for a few days I think mark-node-clean and > mark-subtree-clean commands would be nice additions to the core. > ​Do you have git commit access? If so, please issue a PR (Pull Request). Edward -- You

Re: solution: clearDirty @ nodes when working with chapters/organizational nodes

2017-03-05 Thread john lunzer
After using these for a few days I think mark-node-clean and mark-subtree-clean commands would be nice additions to the core. On Friday, March 3, 2017 at 1:27:00 PM UTC-5, john lunzer wrote: > > A design decision was made in Leo that if you alter the heading/body of > any parent of an @ node

solution: clearDirty @ nodes when working with chapters/organizational nodes

2017-03-03 Thread john lunzer
A design decision was made in Leo that if you alter the heading/body of any parent of an @ node that this node will be marked dirty, ie it will be written to disk when saving the .leo file. After discussion I agree it's the safest option. However, when using chapters and organizational nodes