unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Howard Melman <hmelman@gmail.com>,
	"16214@debbugs.gnu.org" <16214@debbugs.gnu.org>
Subject: bug#16214: [External] : bug#16214: Consistency in dired-, occur-, and grep-mode
Date: Thu, 17 Feb 2022 17:12:57 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488DBF1E0E0973C6DCF3E45F3369@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <lyee41sbhw.fsf@new-host-4.home>

> Dired users with existing muscle memory to enter wdired via
> C-x C-q are unchanged.  Dired users that use f or RET to
> edit a file are unchanged; those that use e to edit a file
> will have to change or bind this themselves.  The emacs
> manual already documents using f to find a file from dired
> and describes RET and e, in that order, as duplicates of f.
> With this, e will change to be a duplicate of C-x C-q.

FWIW -

I don't think `e' in Dired should do what `C-x C-q'
does.  I don't think we ever need a duplicate default
binding for what `C-x C-q' does.

Dired can do lots of things, and can have _lots_ of
default key bindings.  I don't see a good reason to
try to make its bindings correspond to those of
`occur' or `grep-mode'.  Same thing for those two
modes - they can have lots of bindings that are
specific to their own features.

We gave global key bindings for a reason.  That's
the place to provide keys we want to be common
across modes (by default).
___

FWIW, in Dired+ `e' isn't the same as `f'.
`e' is instead a toggle for showing the file:

  View the file on this line in another window in the same frame.
  If it was not already shown there then kill the previous buffer
  visited by a `diredp-visit-*' command.

  If it was already shown there, and if it and Dired are the only
  windows there, then delete its window (toggle : show/hide the file).

Commands `diredp-visit-(next|previous)-file' are
bound to `C-(down|up)'.





  reply	other threads:[~2022-02-17 17:12 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
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                 ` Drew Adams [this message]
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=SJ0PR10MB5488DBF1E0E0973C6DCF3E45F3369@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=16214@debbugs.gnu.org \
    --cc=hmelman@gmail.com \
    /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).