From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54173@debbugs.gnu.org, Augusto Stoffel <arstoffel@gmail.com>
Subject: bug#54173: 28.0.91; Training wheels for query-replace
Date: Thu, 10 Mar 2022 21:44:32 +0200 [thread overview]
Message-ID: <86wnh1mw2n.fsf@mail.linkov.net> (raw)
In-Reply-To: <878rth4nf2.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 10 Mar 2022 20:28:49 +0100")
>> If you think someone might want to display reminders for some rarely used
>> keys, then a variable with a help string would be fine.
>
> I think the likelihood of a user customising such a string is pretty
> much nil -- if they're able to formulate a longer help string here, then
> they'll remember the options they typed out.
I agree that probability tends to zero.
OTOH, there is already such a const:
(defconst query-replace-help "...")
that is used in:
(substitute-command-keys query-replace-help)
So the same way a new const makes sense:
(defconst query-replace-prompt-help "(\\<query-replace-map>\\[help] for help) ")
to be used like this:
(substitute-command-keys query-replace-prompt-help)
that will help Augusto to solve this problem.
next prev parent reply other threads:[~2022-03-10 19:44 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
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 [this message]
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=86wnh1mw2n.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=54173@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--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).