[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16214: Consistency in dired-, occur-, and grep-mode
From: |
Michael Albinus |
Subject: |
bug#16214: Consistency in dired-, occur-, and grep-mode |
Date: |
Mon, 14 Feb 2022 07:52:11 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Richard Stallman <rms@gnu.org> writes:
Hi Richard,
> > > I suspect that v in vc-dir is used rarely enough that people would
> > > not object to a change.
>
> > I use it every single day, and often. Like other people who aren't using
> > magit (but I don't know whether this are many people these days).
>
> I am not sure how to interpret that. Are you saying that
> you intentionally type v (in vc-dir) every day?
> Or that you accidentally type v (in vc-dir) every day?
The former.
> I it is the former, I am surprised that you create a new file every
> day. When I was working on software, I would make changes every day,
> but new files were rare. How is it that you have such frequent
> occasions to put a new file into version control? I'd like to
> understand what leads to this.
'v' in vc-dired means 'vc-next-action'. It does whatever vc command is
appropriate at the given context. In my use case, I apply it in order to
commit a file or fileset. Every single day.
> > > Maybe a better fix would be to make v in vc-dir ask for confirmation.
> > > (I don't know whether it already does that; I may never have used it.)
> > > At least this way typing v by mistake won't cause much trouble.
>
> > There is already some interactive ping-pong, because you have to provide
> > some text, depending on what vc-next-action (the command bound to v in
> > vc-dir) intends to do.
>
> That being so, I would surmise that when you type v by accident,
> nothing very bad happens -- you get asked for input and you type C-g,
> right?
Yes. That's why I vote to keep the 'v' key binding for vc-dired buffers.
Best regards, Michael.
- bug#16214: Consistency in dired-, occur-, and grep-mode, Lars Ingebrigtsen, 2022/02/10
- bug#16214: Consistency in dired-, occur-, and grep-mode, Tak Kunihiro, 2022/02/10
- bug#16214: Consistency in dired-, occur-, and grep-mode, Richard Stallman, 2022/02/11
- bug#16214: Consistency in dired-, occur-, and grep-mode, Michael Albinus, 2022/02/12
- bug#16214: Consistency in dired-, occur-, and grep-mode, Richard Stallman, 2022/02/13
- bug#16214: Consistency in dired-, occur-, and grep-mode,
Michael Albinus <=
- bug#16214: Consistency in dired-, occur-, and grep-mode, Richard Stallman, 2022/02/14
bug#16214: Consistency in dired-, occur-, and grep-mode, Howard Melman, 2022/02/12
- bug#16214: Consistency in dired-, occur-, and grep-mode, Howard Melman, 2022/02/12
- bug#16214: Consistency in dired-, occur-, and grep-mode, Richard Stallman, 2022/02/13
- bug#16214: Consistency in dired-, occur-, and grep-mode, Howard Melman, 2022/02/17
- bug#16214: [External] : bug#16214: Consistency in dired-, occur-, and grep-mode, Drew Adams, 2022/02/17
- bug#16214: Consistency in dired-, occur-, and grep-mode, Tak Kunihiro, 2022/02/19
- bug#16214: Consistency in dired-, occur-, and grep-mode, Howard Melman, 2022/02/20