unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tim Landscheidt <tim@tim-landscheidt.de>
Cc: michael.albinus@gmx.de, 63399@debbugs.gnu.org
Subject: bug#63399: 28.2; Documentation for yes-or-no-p wrong/different between docstring and lispref
Date: Wed, 10 May 2023 19:44:24 +0300	[thread overview]
Message-ID: <83lehw6srb.fsf@gnu.org> (raw)
In-Reply-To: <87cz38rx40.fsf@vagabond.tim-landscheidt.de> (message from Tim Landscheidt on Wed, 10 May 2023 16:04:47 +0000)

> From: Tim Landscheidt <tim@tim-landscheidt.de>
> Cc: Michael Albinus <michael.albinus@gmx.de>,  63399@debbugs.gnu.org
> Date: Wed, 10 May 2023 16:04:47 +0000
> 
> Eli Zaretskii <eliz@gnu.org> wrote:
> 
> >> > But there's no difference if the prompt ends in a space.
> 
> >> Yes. It is just a convenience change, and there's code in the wild which
> >> doesn't use a trailing space in the propmpt, when calling
> >> yes-or-no-p. What would be wrong with my patch? I don't see that it
> >> hurts.
> 
> > I'm sure something will come up.  It isn't an accident that we have
> > danced around this more than once in the past.
> 
> > But if you insist, please install on master, and let's see whose gray
> > hair is more right...
> 
> I support Michael's idea here.

Of course you do.  And I won't argue, I will just say that you don't
have enough gray hair in Emacs development.  Time and again I see us
willing to fix some minuscule issue, and as result introduce subtle
problems and regressions which are frequently worse than the original
issue.  I suspect this is one of those cases.  But I'm willing to
consider the possibility that perhaps this time I will be wrong (yeah,
right).





  reply	other threads:[~2023-05-10 16:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 20:35 bug#63399: 28.2; Documentation for yes-or-no-p wrong/different between docstring and lispref Tim Landscheidt
2023-05-10 10:08 ` Michael Albinus
2023-05-10 14:05   ` Eli Zaretskii
2023-05-10 14:07     ` Michael Albinus
2023-05-10 14:42       ` Eli Zaretskii
2023-05-10 14:57         ` Michael Albinus
2023-05-10 15:44           ` Eli Zaretskii
2023-05-10 16:04             ` Tim Landscheidt
2023-05-10 16:44               ` Eli Zaretskii [this message]
2023-05-10 16:57                 ` Michael Albinus
2023-05-10 16:55             ` Michael Albinus
2023-05-12 10:49             ` Michael Albinus
2023-05-10 13:48 ` Eli Zaretskii
2023-05-10 14:05   ` Michael Albinus

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=83lehw6srb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63399@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=tim@tim-landscheidt.de \
    /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).