[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#34949: 27.0.50; Docstring of `vc-deduce-fileset' incomplete

From: Dmitry Gutov
Subject: bug#34949: 27.0.50; Docstring of `vc-deduce-fileset' incomplete
Date: Fri, 28 Feb 2020 21:22:01 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0

On 28.02.2020 1:15, Juri Linkov wrote:
In any case it seems the best default would be to include to fileset
all files except with the 'unregistered' status.

What other statuses do you want to include except the two I mentioned?

I don't know all possible statuses.

It's documented in the docstring of vc-state.

Then the backend will
handle the files with the 'conflict' status (e.g. to signal an error).

No, it won't signal an error. It will silently commit the changes.

Too bad.  This means we can't collect files into a fileset
behind the scene without user's consent.  The user should have
an overview of the fileset in VC-Dir before committing it.

Thus I'm going to implement this design: when a directory is marked
in Dired, then invoking 'C-x v v' in Dired will open the *vc-dir* buffer
and mark the same directory in it.

Fair enough. I think I preferred your other idea a bit more, but this also sounds workable.

Except... if a directory selected in a VC-Dir buffer contains files in "incompatible" states, vc-next-action should complain as well.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]