From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Alan Mackenzie <acm@muc.de>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Strange use of (run-with-timer 0 nil #'foo args) in do-after-load-evaluation
Date: Sun, 27 Oct 2019 23:57:32 +0200 [thread overview]
Message-ID: <87mudl3l83.fsf@mail.linkov.net> (raw)
In-Reply-To: <87o8y3d4ur.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 26 Oct 2019 15:16:28 +0200")
>>> The current situation seems unsatisfactory; the prompt from
>>> hack-local-variables is more important than the deprecation message,
>>> and shouldn't be obscured by it.
>>
>> It's a kind of general problem with messages, indeed.
>
> Yup. There are several bug reports on this (general) issue of
> asynchronous messages hiding queries. One suggestion has been to extend
> the echo area in these instances, showing the message (perhaps) below
> the prompt. Another is to have the prompt re-assert itself after a
> timeout, making the message disappear.
These bug reports are fixed now when messages are displayed in the
minibuffer, but the problem still exists for the y-or-n-p prompt.
Why y-or-n-p doesn't use normal minibuffer functions?
It can finely use read-from-minibuffer with a keymap where
'y' and 'n' keys are bound to minibuffer-exiting commands.
Then history commands will be available for free, so you don't need
to re-implement minibuffer history commands with `read-char-with-history'.
next prev parent reply other threads:[~2019-10-27 21:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 10:14 Strange use of (run-with-timer 0 nil #'foo args) in do-after-load-evaluation Alan Mackenzie
2019-10-26 12:41 ` Stefan Monnier
2019-10-26 13:16 ` Lars Ingebrigtsen
2019-10-26 16:38 ` Stefan Monnier
2019-10-27 1:01 ` HaiJun Zhang
2019-10-27 21:57 ` Juri Linkov [this message]
2019-10-27 22:29 ` Juri Linkov
2019-10-28 9:41 ` martin rudalics
2019-10-28 2:13 ` Stefan Monnier
2019-10-28 10:45 ` Lars Ingebrigtsen
2019-10-28 22:19 ` Juri Linkov
2019-10-28 23:20 ` Stefan Kangas
2019-10-29 23:39 ` Juri Linkov
2019-10-29 11:38 ` Lars Ingebrigtsen
2019-10-29 23:45 ` Juri Linkov
2019-10-29 23:58 ` Lars Ingebrigtsen
2019-10-30 8:22 ` martin rudalics
2019-10-30 22:10 ` Juri Linkov
2019-10-31 2:00 ` Stefan Monnier
2019-11-03 20:50 ` Juri Linkov
2019-10-26 14:18 ` Alan Mackenzie
2019-10-26 15:27 ` Juanma Barranquero
2019-10-27 21:51 ` Juri Linkov
2019-10-28 3:34 ` 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=87mudl3l83.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).