Hi Miles, Thanks for your comments. I'm forwarding that to the xtla Mailing list.
-- Matthieu
--- Begin Message ---Hi, I've been playing with xtla a bit, and it's shaping up nicely. Together with Stefan's vc-arch, it's nice to finally have some tla support in emacs! I kept track of various nitpicks while using it, and have included a list; most of these are quite minor, but I didn't attempt to fix anything on the assumption that the code's probably still changing quickly and I'd just run into conflicts anyway. The version I used is: [EMAIL PROTECTED] Anyway, here's my list: general: * Perhaps when `tla-make-log-function' is non-nil, `tla-make-log' should check the return value, and if nil, make a normal log file. That way the user's special version can only worry about special cases. * Perhaps some dired-style file management functions, at least those supported by tla (mv, rm). * `M-x tla-bookmarks' gives: tla-bookmarks-cursor-goto: Wrong type argument: arrayp, nil Error in post-command-hook: (void-variable tla-bookmarks-font-lock-keywords) tla-changes: * It always uses the name `*tla-changes*' for the buffer, which means you can use it with multiple trees at the same time. A system like that used by pcl-cvs would be nice (I don't remember the details off hand, but it basically uses *cvs* when there's only one such buffer, and *cvs-mumble* for each when there's more). * If not in a project tree, `tla-changes' should prompt for the tree name similar to tla-inventory -- often I'd rather start out with `changes' and skip `inventory' entirely. [Conversely, maybe tla-inventory _shouldn't_ prompt when already in a tree?] * It would be nice if the `g' command in a *tla-changes* buffer would display a message or modeline frob to indicate that it's doing something. * It would be nice if the `g' command in a *tla-changes* buffer would would retain any existing marks (I often want to check the changes just one last time before committing). * More diff-mode commands should be bound in the *tla-changes* buffer, e.g., `P', and `N'; maybe it can just inherit from the diff-mode keymap? * After committing from a *tla-changes* buffer, it would be good to automatically update the buffer, so there's a clear indication what's changed. * When there are no changes anymore, the `g' command in the *tla-changes* buffer just prints a message in the echo area, and doesn't update the buffer, which can be confusing; it would be better to erase the buffer and perhaps insert the "No changes" description to make it clear what's going on (so work slightly differently than `M-x tla-changes' invoked from another buffer -- in that case, just a message is good). Thanks, -Miles -- Next to fried food, the South has suffered most from oratory. -- Walter Hines Page
--- End Message ---
