GNU bug report logs - #63399
28.2; Documentation for yes-or-no-p wrong/different between docstring and lispref

Previous Next

Full log

Message #8 received at 63399 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Tim Landscheidt <tim <at> tim-landscheidt.de>
Cc: 63399 <at> debbugs.gnu.org
Subject: Re: bug#63399: 28.2; Documentation for yes-or-no-p wrong/different
 between docstring and lispref
Date: Wed, 10 May 2023 12:08:24 +0200

[Message part 1 (text/plain, inline)]

Tim Landscheidt <tim <at> tim-landscheidt.de> writes:

Hi,

> With the big caveat that I have never looked deeper at
> Emacs's C code, the source in src/fns.c does not appear to
> change the prompt given as an argument in any way, but just
> append yes-or-no-prompt to it.
>
> Also, (elisp) Yes-or-No Queries reads (since 7f53446a10ea;
> doc/lispref/minibuf.texi):
>
> | […]
>
> |      Here is an example:
>
> |           (yes-or-no-p "Do you really want to remove everything?")
>
> |           ;; After evaluation of the preceding expression,
> |           ;;   the following prompt appears,
> |           ;;   with an empty minibuffer:
>
> |           ---------- Buffer: minibuffer ----------
> |           Do you really want to remove everything? (yes or no)
> |           ---------- Buffer: minibuffer ----------
>
> | […]
>
> This is not the actual result: (yes-or-no-p "Do you really
> want to remove everything?") gives the prompt "Do you really
> want to remove everything?(yes or no) ", i. e., the space
> before the parenthesis is missing.

I guess we should pad the prompt with a trailing space, if there isn't
any already. As we do in `y-or-no-p'. What about the appended patch?
Documentation must be updated as well, of course.

Best regards, Michael.

[Message part 2 (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.