From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Augusto Stoffel <arstoffel@gmail.com>
Cc: "54173@debbugs.gnu.org" <54173@debbugs.gnu.org>
Subject: bug#54173: [External] : bug#54173: 28.0.91; Training wheels for query-replace
Date: Sun, 27 Feb 2022 16:11:33 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488FD3DA067481B845790BDF3009@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83o82so9yn.fsf@gnu.org>
> > > How about the below?
> > >
> > > (‘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.
Just a quick nit about the proposed prompt text. (Not
commenting on the rest of your exchange; you seem to
be discussing it fruitfully.)
My comment on that text: The clauses separated by
commas each show a key followed by a brief description
of what the key does. _Except_ for "`y'/`n'". It's
not necessarily obvious what the y/n behaviors are.
And even if you think the y/n behaviors are obvious,
it's not so easy to parse the message, splitting it
properly at commas - especially given the inconsistent
treatment of y/n.
1. Consider adding at least some text after `y'/`n'
(maybe "replace this" or just "this" or just "here"?).
2. I wonder if it also might be clearer to drop the
quotes, add a colon, and perhaps to use a semicolon
or slash as separator:
(y/n: replace here / .: replace & exit / ^: back up / ?: help)
versus
(‘y’/‘n’ <what?>, ‘.’ replace & exit, ‘^’ back up, ‘?’ help)
Just a suggestion, to consider both y/n action and
better separation. You may well find other/better
ways to address those two questions.
next prev parent reply other threads:[~2022-02-27 16:11 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 ` Drew Adams [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB5488FD3DA067481B845790BDF3009@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=54173@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.