Matthieu Moy <[EMAIL PROTECTED]> writes: > Hi ! > > Some time ago, I've implemented the *tla-log* feature, keeping track > of which command was executed in which directory, and at what time. > > I think this is very usefull for debugging, and very pedagogical for > our users curious enough to wonder what xtla is doing when he or she > presses a key (Like PCL-CVS tells you what was the last command > executed.) > > This feature was broken by the new tla--run-tla-..., and I'd like to > repair it. > > More than this, I have a plan to considerably improve it : > > * Each process buffer should contain a local variable > tla--process-description, giving the command name, the time at which > the command was ran, the error and process buffers, the buffer from > which it was run, ... > > * The *tla-log* buffer should be an ewoc list of process description. > (Well, actually, a (cons process-description event).) > > * Typing RET or 'p' on an item in the *tla-log* buffer should switch > to the corresponding process buffer. 'e' will switch to the error > buffer, 'b' will open the buffer from which the process was run. > > Doesn't seem too complex to implement, and should be rather usefull. > I'll implement that next week.
Done! We now have to eliminate all occurence to the old tla--run-arch function (still 70 !!). I think this should be our nb 1 priority for the next few days. The code will be much cleaner after that. (Note that logging is disabled for the old function) -- Matthieu
