From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 54173@debbugs.gnu.org
Subject: bug#54173: 28.0.91; Training wheels for query-replace
Date: Sun, 27 Feb 2022 11:24:53 +0200 [thread overview]
Message-ID: <83sfs4oe56.fsf@gnu.org> (raw)
In-Reply-To: <87sfs4wv35.fsf@gmail.com> (message from Augusto Stoffel on Sun, 27 Feb 2022 09:51:42 +0100)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: 54173@debbugs.gnu.org
> Date: Sun, 27 Feb 2022 09:51:42 +0100
>
> > But since '?' produces a more detailed help, and that help text stays
> > on display thereafter, do we really need one more variant? Maybe the
> > default message could be expanded instead (but not to such a long
> > text, which would resize the mini-window in many cases)?
>
> I think ‘y’ and ‘n’ are intuitive enough that they don't need a
> reminder. But mentioning the more uncommon ones (‘.’ and so on) without
> talking about ‘y’ and ‘n’ is weird.
How about the below?
(‘y’/‘n’, ‘.’ replace & exit, ‘^’ back up, ‘?’ help)
An alternative is to have C-h and F1 temporarily show a longer line
with more commands.
> One idea would be to choose between the short and long messages based on
> the size of the miniwindow as well as the length regexp and replacement
> text.
That could also be a possibility.
next prev parent reply other threads:[~2022-02-27 9:24 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 [this message]
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
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=83sfs4oe56.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54173@debbugs.gnu.org \
--cc=arstoffel@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).