Neilen Marais <[EMAIL PROTECTED]> writes:

> I see. Now that I can get it to work, I must say it's a useful feature :) 
> Perhaps the easiest solution would simply be to insert no text at all if
> the changes list can't be found.

Trivial, but very good idea indeed. I propose the following:

* If the list can be computed, insert/update it

* Otherwise

  - If the log buffer doesn't contain the file list, do not print
    anything.

  - If there was already a message, then replace it with this
    <can't compute list>. The user will probably understand since he
    will see this message /only/ after seeing the expected behavior.

> Or otherwise, doing what is needed to make it work if the user
> invoked it with C-x T c from another buffer.

More complex than it seems, since to compute the list, you need to run
"status" or "diff", which is a rather long operation, and I want to
keep the access to the log buffer instantaneous. A solution would be
to make an asynchronous call, but then this means the process sentinel
would modify the buffer that the user is editing, I don't think that's
a good idea.

BTW, I think this feature should be ported to DVC.

-- 
Matthieu

Reply via email to