LeoPy.leo or LeoPyRef.leo are not the leo files I'm concerned about.
I want to collaborate with my colleagues on the forests of system
configuration I maintain, and we are frequently committing to our
(internal) repository. It is the rare exception that I'm working on
something I want only in my own copy. If something is irrelevant
cruft, just collapse the node; to concentrate on an area, hoist(*)!
The "Recovered Nodes" give me hope that a humanly useful
representation of changes is possible. I need to study that code.
The result is so much better than opaque XML operations.
- Stephen
* (reminder to self: check hoist description in Chapter 3.)
--
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.
