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 15:43:27 -0500 [thread overview]
Message-ID: <lyczjr6ck0.fsf@new-host-5.home> (raw)
In-Reply-To: <20131221.224043.270400015.tkk@misasa.okayama-u.ac.jp>
Howard Melman <hmelman@gmail.com> writes:
> 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.
Actually, I this think is still viable:
> To have consistency on edition of buffer at dired-/occur-/grep-mode,
> (1) addition of two key-binds, "e" to both (dired-toggle-read-only)
> and (wgrep-change-to-wgrep-mode)
In occur-mode `e` already enters `occur-edit mode`.
In grep-mode `e` is unbound. `wgrep` is in nongnu elpa so I don't
know if `grep-mode` can reference it. But if not, perhaps it could
reserve this key for a wgrep-like function with a comment. `wgrep`
could be updated to add the binding or just document it as a
possibility.
In dired-mode `dired-toggle-read-only` is bound to `C-x C-q`
and `dired-find-file` is bound to `e`, `f` *and* `RET` (and
`f` is the one the emacs manual mentions first). If just
`e` were changed to invoke `dired-toggle-read-only` then
existing users in `dired-mode` can still use `f` and `RET`
to edit a file or rebind `e`.
Changing just one binding which already has two other equally
convenient (single key) and intuitive bindings doesn't seem too
invasive IMHO to fix something that, as you say, if it were designed
today would indeed be a priority.
--
Howard
next prev parent reply other threads:[~2022-02-12 20:43 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 [this message]
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=lyczjr6ck0.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).