Matthieu Moy <[EMAIL PROTECTED]> writes:
> 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 :-)
Very cool! I hit one small problem when I restarted emacs (perhaps this
is my problem ;o)--it seemed to run recursively even where I didn't
have any subtrees, and it was causing some strange behaviour. I've taken
a (very) quick look at it, and replacing:
(let ((subtrees (split-string
(with-current-buffer
output (buffer-string)) "\n")))
with:
(let ((subtrees (split-string
(with-current-buffer
output (buffer-string)) "\n" t)))
Works For Me. It was just that SPLIT-STRING was returning (""). Does
this sound right?
Cheers,
Mark
--
Mark Triggs
<[EMAIL PROTECTED]>
