From: Howard Melman <hmelman@gmail.com>
To: 16214@debbugs.gnu.org
Subject: bug#16214: Consistency in dired-, occur-, and grep-mode
Date: Sat, 12 Feb 2022 14:12:01 -0500 [thread overview]
Message-ID: <lyh7936gse.fsf@new-host-5.home> (raw)
In-Reply-To: <20131221.224043.270400015.tkk@misasa.okayama-u.ac.jp>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> If these modes were designed today, then having the keys be more
> consistent would indeed be a priority. However, these bindings have
> been around for decades, and changing them would break the muscle memory
> of many people, and be highly annoying, so we can't do that.
I understand though am diaappointed. I'd argue my muscle
memory would be improved if I didn't have to remember three
different sets of some these similar bindings. And of
course existing users are able to rebind them if they wish
and are certainly more able to do so than new users. But
this argument has been made before.
> Individual users are free to rebind these as they wish, of course, and
> somebody properly motivated could make an ELPA package to unify these
> bindings, but I don't think there's anything realistic that can be done
> on the Emacs side here, so I'm therefore closing this bug report.
FWIW I do the following:
(with-eval-after-load 'grep-mode
(define-key grep-mode-map (kbd "o") #'compile-goto-error)
(define-key grep-mode-map (kbd "C-o") #'compilation-display-error))
I think adding these binding to emacs wouldn't break
any muscle memory and would unify at least two categories.
I'd also love to see one common way of entering wdired,
occur-edit and wgrep. The burden of maintaining this muscle
memory is IMHO silly.
--
Howard
next prev parent reply other threads:[~2022-02-12 19: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 [this message]
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=lyh7936gse.fsf@new-host-5.home \
--to=hmelman@gmail.com \
--cc=16214@debbugs.gnu.org \
/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).