From: Augusto Stoffel <arstoffel@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54173@debbugs.gnu.org
Subject: bug#54173: 28.0.91; Training wheels for query-replace
Date: Sun, 27 Feb 2022 14:46:18 +0100 [thread overview]
Message-ID: <87tuckjuc5.fsf@gmail.com> (raw)
In-Reply-To: <87tucksbey.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 27 Feb 2022 14:10:13 +0100")
On Sun, 27 Feb 2022 at 14:10, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Augusto Stoffel <arstoffel@gmail.com> writes:
>
>> - (define-key map "y" 'act)
>> - (define-key map "n" 'skip)
>> (define-key map "Y" 'act)
>> + (define-key map "y" 'act)
>> (define-key map "N" 'skip)
>> - (define-key map "e" 'edit-replacement)
>> + (define-key map "n" 'skip)
>> (define-key map "E" 'edit-replacement)
>> + (define-key map "e" 'edit-replacement)
>
> This seems unrelated, and just moves bindings around?
This is so that 'substitute-command-keys' pick up the right key for each
command, that is, the lower cased ones.
>>> > (‘y’/‘n’, ‘.’ replace & exit, ‘^’ back up, ‘?’ help)
>>>
>>> I find this better than the status quo. I've attached the patch.
>>
>> Thanks. Let's wait a bit to let others chime in and express their
>> opinions.
>
> I'm not sure I understood the patch. Is the proposal to append all that
> to "Query replacing foo with bar"? It'll make prompts commonly be
> longer than a line, and it's pretty noisy, so if that's the proposal,
> I'm against it.
Well, yes, that's the proposal...
At least now that string is a defvar that you can set to nil if you want
to save some columns :-)
> The help is on `?', so I don't see the point, either.
I think it's just nice to have a constant reminder of ‘.’ and ‘^’. Of
course I'll remember them after all this discussion, but until now I
could never quite recall them when the occasion arose.
next prev parent reply other threads:[~2022-02-27 13:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 22:15 bug#54173: 28.0.91; Training wheels for query-replace Augusto Stoffel
2022-02-27 6:54 ` Eli Zaretskii
2022-02-27 7:55 ` Augusto Stoffel
2022-02-27 8:23 ` Eli Zaretskii
2022-02-27 8:51 ` Augusto Stoffel
2022-02-27 9:24 ` Eli Zaretskii
2022-02-27 10:17 ` Augusto Stoffel
2022-02-27 10:55 ` Eli Zaretskii
2022-02-27 16:11 ` bug#54173: [External] : " Drew Adams
2022-02-27 13:10 ` Lars Ingebrigtsen
2022-02-27 13:46 ` Augusto Stoffel [this message]
2022-03-03 16:41 ` Augusto Stoffel
2022-03-10 19:24 ` Juri Linkov
2022-03-10 19:28 ` Lars Ingebrigtsen
2022-03-10 19:44 ` Juri Linkov
2022-03-12 16:58 ` Lars Ingebrigtsen
2022-03-10 19:20 ` Juri Linkov
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=87tuckjuc5.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=54173@debbugs.gnu.org \
--cc=larsi@gnus.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).