Matthieu Moy <[EMAIL PROTECTED]> writes:

> Stefan Reichör <[EMAIL PROTECTED]> writes:
>
>> Stephen Leake <[EMAIL PROTECTED]> writes:
>>
>>> I'm adding a 'dvc-status-mode', which will present an interface
>>> similar to pcvs. I intend to use it as the primary user interface for
>>> DVC. This overlaps some of the current dvc-diff-mode function; perhaps
>>> we can simplify dvc-diff-mode in the future.
>>
>> I had already implemented a dvc-status, but we removed it again, since
>> Matthieu argumented, that the dvc-diff mode should handle that also, see:
>>
>> https://mail.gna.org/public/xtla-el-dev/2006-03/msg00120.html
>>
>> Matthieu, what is your opinion in this point now?
>
> Well, perhaps dvc-diff-mode is not the best name for this mode, but
> the idea is that it is a superset of a diff-mode and a status-mode.
> You get a short summary at the top, and a diff below. Since it is
> possible to have a buffer in diff-mode without having the diff at the
> bottom, that mode really suits the need to run "status".

Hmm. I had not noticed that option. How do I get that?

Sometimes I find the diff listing useful, but mostly not.

> Implementing a new diff-mode, and removing the summary part from the
> diff-mode would be a real loss of functionality IMHO. The summary is
> really the part you want to start with as soon as the diff is more
> than a screen long, and you have the key 'j' to switch from the
> summary to the diff, and vice-versa.

Actually, I'm implementing a new status-mode, and leaving the current
diff-mode alone.

I'm using symbols for the file status (instead of letters), and a CL
struct for the ewoc data. So it is easier to understand and edit.
Perhaps it would make sense to change the current diff-mode to be more
like what I want.

--
-- Stephe


_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev

Reply via email to