GNU bug report logs - #34939
Some minibuffer behaviour is annoying

Previous Next

Full log

Message #119 received at 34939 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 34939 <at> debbugs.gnu.org, pinkanon pinkanon <pinkanon.pinkanon <at> yandex.ru>,
 Dmitry Gutov <dgutov <at> yandex.ru>
Subject: Re: bug#34939: Some minibuffer behaviour is annoying
Date: Fri, 31 May 2019 00:35:16 +0300

>> > 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.