PR #4386 <https://github.com/leo-editor/leo-editor/pull/4386> is now in the 
"devel" branch.


This PR makes huge improvements to @clean. We have seen nothing like it 
since @clean first appeared in April 2015. We can now use @clean nodes on 
huge repos!


This PR fixes bugs and hangnails we've been living with since day one:


- Leo will detect changes to external @clean files, whether or not Leo is 
running.

- Leo leaves whitespace unchanged when importing to @clean or @auto. Why 
has nobody complained before?

- When importing or updating @clean trees, Leo will move leading blank 
lines to the start of the previous node. These moves happen *only in 
newly-updated nodes*, so you can "undo" these moves if you like. But such 
moves are almost always what we want.


*A spectacular new feature: the update review tree*


Whenever Leo detects updated nodes in @clean trees, Leo will create a new 
top-level node called Updated @clean/@auto nodes. Let's call this node and 
its descendants the *update report tree*:


- This top-level node contains *update organizer nodes*  for each updated 
file. The name of these nodes has the form: Updated from: whatever.py.

- Leo creates clones of each updated node as children of these organizer 
nodes.

- Leo puts the diffs of all the updated nodes from each file in the 
appropriate update organizer node.


The update review tree ranks with Leo's killer git-diff and cff commands! 
You can retain, change, or delete any part of the update report tree as you 
like:


- Deleting any part of this tree has affect any external file.

- As with the cff and git-diff commands, changing cloned nodes *will *change 
the corresponding external file.


*Conclusion*


PR #4386 <https://github.com/leo-editor/leo-editor/pull/4386> is a huge 
step forward for Leo. Please report any problems immediately.


Edward

-- 
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 view this discussion visit 
https://groups.google.com/d/msgid/leo-editor/255d21c3-7a4d-4602-bcfd-81859dc74718n%40googlegroups.com.

Reply via email to