From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21396@debbugs.gnu.org
Subject: bug#21396: 25.0.50; read-key's prompt is not visible
Date: Thu, 03 Sep 2015 20:42:05 +0200 [thread overview]
Message-ID: <87zj13fipu.fsf@gnu.org> (raw)
In-Reply-To: <83d1xz9xjz.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 03 Sep 2015 21:18:08 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> >> 1. emacs -Q
>> >> 2. eval (read-key "Gimme Key: ") in *scratch*
>> >> the key will be read but the prompt is not shown in the minibuffer
>> > [...]
>> >> commit 5dc644a6b01e2cf950ff617ab15be4bf1917c38c
>> >> Author: Stefan Monnier <monnier@iro.umontreal.ca>
>> >> Date: Tue Sep 1 21:14:18 2015 -0400
>> >> Generalize the prefix-command machinery of C-u
>> >
>> > Hmm... I'll look into it.
>>
>> Great, thanks. Meanwhile others have seen that issue, too. See the
>> thread on emacs-devel.
>
> I really hope Stefan will NOT fix this. It's IMO the wrong way of
> dealing with such issues.
>
> 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.
>
> 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.
>
> 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'm guilty of having (fset 'yes-or-no-p 'y-or-n-p) in my ~/.emacs, too,
but what does this have to do with this issue? The problem is that no
prompt of any `read-key' is visible, `y-or-n-p' is just the most
prominent place where this pops up.
Bye,
Tassilo
next prev parent reply other threads:[~2015-09-03 18:42 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 [this message]
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
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zj13fipu.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=21396@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.