From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Andreas Schwab <schwab@linux-m68k.org>
Cc: 38785@debbugs.gnu.org
Subject: bug#38785: 26.3; `y-or-n-p' leaves prompt and response in echo area
Date: Sun, 29 Dec 2019 06:14:40 -0800 (PST) [thread overview]
Message-ID: <9f59791d-d4b5-4d41-b6e1-0a8428681c68@default> (raw)
In-Reply-To: <<83blrrns4o.fsf@gnu.org>>
> > > I think `y-or-n-p' should probably just use `(sit-for 1)'
> > > after it shows the prompt + answer,
> >
> > That would always delay the caller of y-or-n-p by one second. I'm
> > pretty sure that would be highly annoying.
>
> Yes. And besides, this area underwent significant changes since Emacs
> 26.3, so I suggest to try the latest emacs-27 branch before continuing
> the discussion.
`read-key', and functions like `y-or-n-p'
that use it or do the same thing, should not
be made to read from the minibuffer.
The fact that such functions have prompted
using the echo area is bad enough. Making
them read from the minibuffer is even worse.
That's my opinion about (my understanding of)
those "significant changes". Doing that just
introduces a new (design) bug that should,
and will hopefully someday, be fixed.
next parent reply other threads:[~2019-12-29 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<787722a4-9679-4160-903d-d9de42801ddf@default>
[not found] ` <<5561aae8-fa46-4228-833a-912fc49d789e@default>
[not found] ` <<87blrrwlsf.fsf@hase.home>
[not found] ` <<83blrrns4o.fsf@gnu.org>
2019-12-29 14:14 ` Drew Adams [this message]
2019-12-28 22:55 bug#38785: 26.3; `y-or-n-p' leaves prompt and response in echo area Drew Adams
2019-12-28 23:30 ` Drew Adams
2019-12-29 8:58 ` Andreas Schwab
2019-12-29 14:06 ` Eli Zaretskii
2019-12-29 14:08 ` Drew Adams
2019-12-29 14:29 ` Andreas Schwab
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=9f59791d-d4b5-4d41-b6e1-0a8428681c68@default \
--to=drew.adams@oracle.com \
--cc=38785@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@linux-m68k.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).