I'm happy enough to share my enthusiasm here :-)
My last few patches bring a new feature to the *tla-changes* buffer,
very usefull for projects using configurations.
This is my case, I work on a project with another nested project. Very
often, I run M-x tla-changes RET in the root of the project, then
commit and so on, but I forget the nested tree. (This is particularly
annoying when I go to another machine, update, and realize that I miss
some modifications !)
I won't do anymore because tla changes is now run recursively by xtla:
,----[ xtla.texinfo ]
| If your tree contains nested trees, then XTLA will display the list of
| nested trees at the top of the changes buffer. They are marked with a
| @code{T} so that you can distinguish them from the modified files.
| While computing, they have the status @code{?}, and this becomes
| @code{M} (resp. @code{-}) when the recursively called @code{tla}
| process exits if there are some changes (resp. no changes) in the
| nested tree.
|
| To view the details of the changes, type @code{RET} on a nested tree
| entry to open the corresponding changes buffer. To come back to the
| root of the project, type @code{^}.
`----
Pfiouuu ! One big item removed from the TODO list :-)
Do you think of any other commands that should be run recursively too?
--
Matthieu
