From: Robert Pluim <rpluim@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Stefan Kangas <stefankangas@gmail.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: master 7f53446: Doc fix for y-or-n-p; trailing space is no longer needed
Date: Wed, 04 Jan 2023 17:07:37 +0100 [thread overview]
Message-ID: <87mt6yi8qe.fsf@gmail.com> (raw)
In-Reply-To: <SJ0PR10MB54889EEBCE879F891329E7E8F3F59@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Wed, 4 Jan 2023 15:53:59 +0000")
>>>>> On Wed, 4 Jan 2023 15:53:59 +0000, Drew Adams <drew.adams@oracle.com> said:
>> (but `yes-or-no-p' should be fixed to add a space if there
>> isnʼt one).
Drew> I'm not following this thread, so apologies if
Drew> my comment is irrelevant or misguided.
If you were, your comments would have been shorter
- `y-or-n-p' has, since emacs 24.3 or so, appended a space to the prompt
if there wasnʼt one
- `yes-or-no-p' doesnʼt mess with the prompt
This discussion is about the documentation of those two facts, which
needs adjusting since itʼs currently incorrect. There was a suggestion
by me to maybe align `yes-or-no-p' behaviour (what you call "dwim") to
match `y-or-n-p', but since thatʼs 'legacy' I doubt itʼs going to be
done.
Robert
--
next prev parent reply other threads:[~2023-01-04 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210916073852.6025.85941@vcs0.savannah.gnu.org>
[not found] ` <20210916073853.B90BA20ABE@vcs0.savannah.gnu.org>
2023-01-03 14:31 ` master 7f53446: Doc fix for y-or-n-p; trailing space is no longer needed Robert Pluim
2023-01-03 15:33 ` Stefan Kangas
2023-01-03 15:59 ` Robert Pluim
2023-01-04 8:43 ` Jean Louis
2023-01-04 10:10 ` Robert Pluim
2023-01-04 15:53 ` [External] : " Drew Adams
2023-01-04 16:07 ` Robert Pluim [this message]
2023-01-04 16:12 ` Drew Adams
2023-01-04 16:14 ` Robert Pluim
2023-01-04 17:31 ` Eli Zaretskii
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=87mt6yi8qe.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@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).