From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Dmitry Gutov <dgutov@yandex.ru>,
34939@debbugs.gnu.org,
pinkanon pinkanon <pinkanon.pinkanon@yandex.ru>
Subject: bug#34939: Some minibuffer behaviour is annoying
Date: Fri, 31 May 2019 00:35:16 +0300 [thread overview]
Message-ID: <87tvdbmxrf.fsf@mail.linkov.net> (raw)
In-Reply-To: <c836f2cf-c57e-4d22-8744-c6443d756eb3@default> (Drew Adams's message of "Thu, 30 May 2019 14:00:27 -0700 (PDT)")
>> > I haven't been following this thread. But it looks
>> > like this will use `minibuffer-message' for errors
>> > raised during minibuffer input, and block `message',
>> > except for logging. Is that right?
>>
>> No, it won't block messages.
>
> It will block `message', not messages. It will hijack
> `message' to effect instead `minibuffer-message'.
>
> That's not right or fair. Code that calls `message'
> should get `message' behavior.
What `message' are you talking about? Currently `message'
is not called during error processing at all.
>> Currently it requires the user to wait 2 seconds
>> before the user can see the minibuffer contents again.
>
> No, it does not. User input cancels the `message'
> text.
It's dangerous and error-prone to type any keys blindly
while the minibuffer contents is obscured by the error message.
next prev parent reply other threads:[~2019-05-30 21:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 19:13 bug#34939: Some minibuffer behaviour is annoying pinkanon pinkanon
2019-03-22 16:57 ` Dmitry Gutov
2019-03-23 2:32 ` Richard Stallman
2019-03-23 9:46 ` Dmitry Gutov
2019-03-23 9:50 ` Eli Zaretskii
2019-03-23 11:24 ` Dmitry Gutov
2019-03-23 12:18 ` pinkanon pinkanon
[not found] ` <<83o961q5rr.fsf@gnu.org>
2019-03-23 15:51 ` Drew Adams
2019-03-31 19:50 ` Juri Linkov
2019-03-31 19:49 ` Juri Linkov
2019-03-31 20:29 ` Juri Linkov
2019-04-01 13:08 ` Dmitry Gutov
2019-04-01 20:31 ` Juri Linkov
2019-04-01 21:53 ` Dmitry Gutov
2019-04-03 20:50 ` Juri Linkov
2019-05-19 20:16 ` Juri Linkov
2019-04-01 10:10 ` pinkanon pinkanon
2019-04-01 20:25 ` Juri Linkov
2019-04-02 18:25 ` pinkanon pinkanon
2019-04-01 13:03 ` Dmitry Gutov
2019-04-01 20:29 ` Juri Linkov
2019-04-07 20:43 ` Juri Linkov
2019-04-07 23:09 ` Dmitry Gutov
2019-04-08 19:47 ` Juri Linkov
2019-04-08 22:00 ` Drew Adams
2019-04-08 23:06 ` Dmitry Gutov
2019-04-08 23:32 ` Drew Adams
2019-04-08 23:37 ` Dmitry Gutov
2019-04-08 23:59 ` Drew Adams
2019-04-09 0:11 ` Dmitry Gutov
2019-04-09 18:26 ` Drew Adams
2019-05-24 22:49 ` Dmitry Gutov
2019-05-27 20:15 ` Juri Linkov
2019-05-27 20:58 ` Dmitry Gutov
2019-05-29 21:53 ` Juri Linkov
2019-05-29 22:26 ` Drew Adams
2019-05-30 19:50 ` Juri Linkov
2019-05-30 21:00 ` Drew Adams
2019-05-30 21:35 ` Juri Linkov [this message]
2019-06-03 20:27 ` Juri Linkov
2019-06-04 15:15 ` Dmitry Gutov
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=87tvdbmxrf.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=34939@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=drew.adams@oracle.com \
--cc=pinkanon.pinkanon@yandex.ru \
/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.