I have some comments about tla--dead-process-buffer-queue. > (kill-buffer (car tla--dead-process-buffer-queue))
I think this is a bit danger. How do you think introduce "*tla-trash*"? Before killing a buffer in tla--dead-process-buffer-queue automatically, the contents of the buffer is appended to *tla-trash* with time stamp and executed command line. *tla-trash* will become too long, however better than be lost, especially for debugging. > (defcustom tla-number-of-dead-process-buffer 20 Now the queue is managed by the length. How do you think use timer instead of timer? The last is question. As far as reading xtla-core.el, there is no relationship between the buffer management codes and the process management codes. e.g. buffers created by tla--new-process-buffer and tla--new-error-buffer are not managed by tla--buffers-tree. We need a kind of C-x C-b for xtla related buffers. Masatake
