unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Robert Pluim <rpluim@gmail.com>, Stefan Kangas <stefankangas@gmail.com>
Cc: "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, 4 Jan 2023 15:53:59 +0000	[thread overview]
Message-ID: <SJ0PR10MB54889EEBCE879F891329E7E8F3F59@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <874jt6k3uc.fsf@gmail.com>

> (but `yes-or-no-p' should be fixed to add a space if there
> isnʼt one).

I'm not following this thread, so apologies if
my comment is irrelevant or misguided.

I disagree that functions such as `yes-or-no-p'
should mess with the prompt.  If a user wants
a space after the colon, and the user forgets
to add one, that's on the user.

If a user wants NO space after the colon for
some reason, however misguided the author of
`yes-or-no-p' might think that choice is, it
should be respected - there's no reason _not_
to respect it.

`yes-or-no-p' and the like shouldn't try to
second-guess users.  Don't let it suffer from
"dwim" lameness, please.  It's up to users to
provide the prompt text they want - they have
tons of ways to do that, including `format'.

Pretty much all of the prompting functions
that append a space, or a colon plus a space,
are misguided.  OK, there's legacy, and we
accommodate that.  But let's please not ADD
to the problem by introducing more examples
of it.  Not willingly and knowingly, at any
rate.

Again, I'm not following this thread.  But
even the Subject line bit "trailing space is
no longer needed" makes me cringe, at least
in my ignorance of what "fix" is intended.

Lots of what exists might be considered "no
longer needed" by someone.  Whether users
already make use of it shouldn't be ignored.

  reply	other threads:[~2023-01-04 15:53 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           ` Drew Adams [this message]
2023-01-04 16:07             ` [External] : " Robert Pluim
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=SJ0PR10MB54889EEBCE879F891329E7E8F3F59@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@gmail.com \
    --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).