From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"46594@debbugs.gnu.org" <46594@debbugs.gnu.org>
Subject: bug#46594: [External] : bug#46594: Use short answers
Date: Thu, 25 Feb 2021 11:20:34 +0200 [thread overview]
Message-ID: <87a6rsec65.fsf@mail.linkov.net> (raw)
In-Reply-To: <SA2PR10MB44747CFABF3AEF3D992B097EF39F9@SA2PR10MB4474.namprd10.prod.outlook.com> (Drew Adams's message of "Wed, 24 Feb 2021 23:55:30 +0000")
> I'm not sure we should include this:
>
> and giving the wrong answer would have serious consequences
>
> That's not necessary, IMO. Not even if you change
> "would" (which is wrong) to "could".
I copied this text verbatim from the Emacs manual
from the node (info "(emacs) Yes or No Prompts"):
The second type of yes-or-no query is typically employed if giving
the wrong answer would have serious consequences; it thus features a
longer prompt ending with ‘(yes or no)’.
Now I noticed it has "if" before.
> It's enough to say that presumably yes-or-no-p is
> used so you take time and perhaps think more about
> the answer. No need to imply serious consequences.
>
> Why do we say this?
>
> In this case it means also obeying the value of
> `y-or-n-p-use-read-key'.
>
> Doesn't that follow, if the behavior is that of
> y-or-n-p (I don't know)? If it does, then just
> refer them to the doc for y-or-n-p; don't repeat
> any of that doc here.
Ok.
next prev parent reply other threads:[~2021-02-25 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 18:59 bug#46594: Use short answers Juri Linkov
2021-02-22 15:13 ` Lars Ingebrigtsen
2021-02-22 17:13 ` bug#46594: [External] : " Drew Adams
2021-02-24 18:44 ` Juri Linkov
2021-02-24 19:26 ` Eli Zaretskii
2021-02-24 19:49 ` Juri Linkov
2021-02-24 20:27 ` Eli Zaretskii
2021-02-24 20:50 ` Juri Linkov
2021-02-25 15:04 ` Eli Zaretskii
2021-02-25 18:45 ` Juri Linkov
2021-02-24 23:55 ` Drew Adams
2021-02-25 9:20 ` Juri Linkov [this message]
2021-02-25 16:40 ` Drew Adams
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=87a6rsec65.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=46594@debbugs.gnu.org \
--cc=drew.adams@oracle.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).