unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Richard Stallman <rms@gnu.org>
Cc: 16214@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
	tkk@misasa.okayama-u.ac.jp, roland@hack.frob.com,
	josh@foxtail.org
Subject: bug#16214: Consistency in dired-, occur-, and grep-mode
Date: Sat, 12 Feb 2022 09:16:49 +0100	[thread overview]
Message-ID: <877da04hzi.fsf@gmx.de> (raw)
In-Reply-To: <E1nIjXL-00056r-BW@fencepost.gnu.org> (Richard Stallman's message of "Fri, 11 Feb 2022 22:57:27 -0500")

Richard Stallman <rms@gnu.org> writes:

Hi Richard,

>   >   For example, `v' in Dired opens a file in view mode,
>   > > so often I type `v' in vc-dir, but it registers the file in version
>   > > control instead of opening in view mode.  I have no idea how to avoid
>   > > this inconsistency.
>
> 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).

> 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.

Best regards, Michael.





  reply	other threads:[~2022-02-12  8:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21 13:40 bug#16214: Consistency in dired-, occur-, and grep-mode Tak Kunihiro
2013-12-21 19:23 ` Drew Adams
2013-12-21 20:15 ` Josh
2013-12-21 21:30   ` Juri Linkov
2013-12-22 11:48     ` Tak Kunihiro
2013-12-22 21:44       ` Juri Linkov
2013-12-23 11:34         ` Tak Kunihiro
2013-12-23 21:52           ` Juri Linkov
2013-12-24 23:15             ` Tak Kunihiro
2013-12-25 20:57               ` Juri Linkov
2013-12-28  9:57                 ` Tak Kunihiro
2022-02-10  8:27         ` Lars Ingebrigtsen
2022-02-10  9:26           ` Tak Kunihiro
2022-02-10 11:37             ` Lars Ingebrigtsen
2022-02-11  5:54               ` Tak Kunihiro
2022-02-12  3:57           ` Richard Stallman
2022-02-12  8:16             ` Michael Albinus [this message]
2022-02-14  4:13               ` Richard Stallman
2022-02-14  6:52                 ` Michael Albinus
2022-02-15  4:30                   ` Richard Stallman
2022-02-12 19:12           ` Howard Melman
2022-02-12 20:43             ` Howard Melman
2022-02-14  4:14               ` Richard Stallman
2022-02-17 16:28               ` Howard Melman
2022-02-17 17:12                 ` bug#16214: [External] : " Drew Adams
2022-02-20  1:43                 ` Tak Kunihiro
2022-02-20 18:17                   ` Howard Melman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877da04hzi.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=16214@debbugs.gnu.org \
    --cc=josh@foxtail.org \
    --cc=larsi@gnus.org \
    --cc=rms@gnu.org \
    --cc=roland@hack.frob.com \
    --cc=tkk@misasa.okayama-u.ac.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).