unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Tassilo Horn <tsdh@gnu.org>
Cc: 21396@debbugs.gnu.org
Subject: bug#21396: 25.0.50; read-key's prompt is not visible
Date: Thu, 3 Sep 2015 11:27:18 -0700 (PDT)	[thread overview]
Message-ID: <d441c9e4-9d78-4915-9d9f-fea001f12daf@default> (raw)
In-Reply-To: <<83d1xz9xjz.fsf@gnu.org>>

> If typing yes<RET> is too much in some situations, and just y is
> enough, we should not call yes-or-no-p in those situations. AFAIU,
> the only reason to call the latter is when the question is about
> some serious matter, so we want to avoid the possibility of mistakenly
> pressing just one (wrong) key.  So if some of these situations aren't
> so grave, let's call y-or-n-p instead.

Agreed.  But that's a decision for Emacs, and it is a judgment
call to try to fit what is generally appropriate in that context.

That's different from what a given user might want.

So yes, Emacs should pick the right function to use.
And yes, users should be able to choose something else,
if they really want to.  (Personally, I stick with what
Emacs decides, here.)

> And if there are people who still want to press y or n, even when they
> might err and pay dearly for their mistakes, then we could have an
> option to have yes-or-no-p call y-or-n-p instead.

Yes.

> But using a defalias here is a kludge; asking Emacs maintenance to
> support such kludges means extra overhead and tricky code for no good
> reason.  I think we should simply say no to such requests.  We have
> more than enough work on our hands already, no need for gratuitous
> additions, thank you.

I agree that a user option is more appropriate than defaliasing.





  parent reply	other threads:[~2015-09-03 18:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 20:14 bug#21403: 25.0.50; invisible y-or-n-p prompt Mark Oteiza
2015-09-03 20:03 ` Stefan Monnier
2015-09-02  6:16   ` bug#21396: 25.0.50; read-key's prompt is not visible Tassilo Horn
2015-09-03 15:12     ` Stefan Monnier
2015-09-03 17:50       ` Tassilo Horn
2015-09-03 18:03         ` Eli Zaretskii
2015-09-03 18:36           ` Tassilo Horn
2015-09-03 18:18         ` Eli Zaretskii
2015-09-03 18:42           ` Tassilo Horn
2015-09-04  6:38             ` Eli Zaretskii
2015-09-04  8:04               ` Tassilo Horn
2015-09-04  8:38                 ` Eli Zaretskii
2015-09-04  9:27                   ` Tassilo Horn
2015-09-03 20:10           ` Stefan Monnier
2015-09-03 20:12             ` Dmitry Gutov
     [not found]       ` <<87egifgzog.fsf@gnu.org>
     [not found]         ` <<83d1xz9xjz.fsf@gnu.org>
2015-09-03 18:27           ` Drew Adams [this message]
     [not found]     ` <handler.21396.D21403.144131058918410.notifdone@debbugs.gnu.org>
2015-09-03 20:07       ` bug#21396: closed (Re: bug#21403: 25.0.50; invisible y-or-n-p prompt) Tassilo Horn
2015-09-03 23:02   ` bug#21403: 25.0.50; invisible y-or-n-p prompt Mark Oteiza
2015-09-07 17:17     ` Stefan Monnier
2015-09-07 17:28     ` Stefan Monnier
2015-09-07  1:04 ` Chris Feng

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=d441c9e4-9d78-4915-9d9f-fea001f12daf@default \
    --to=drew.adams@oracle.com \
    --cc=21396@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=tsdh@gnu.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).