Subject: bug#34939: Some minibuffer behaviour is annoying

From: Juri Linkov <[email-masked]>
Date: Thu, 30 May 2019 22:50:16 +0300

>> Here is a complete 1-to-1 rewrite of the C function ‘print_error_message’
>> in Lisp that now can be used for more user-friendly displaying error messages
>                                        ^^^^^^^^^^^^^
>> in the minibuffer
>
> 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.

> If not, just what does this change represent?

It will display messages together with the minibuffer contents
instead of replacing it.

Currently it requires the user to wait 2 seconds
before the user can see the minibuffer contents again.
Most often, this happens after typing M-n to see if any default values
are available, and it replaces the minibuffer contents with the message
“End of history; no default available”.  I have to wait several times
per day for this message to go away.  Totally it takes ~1 minute per day,
~300 minutes (5 hours) per year, and ~50 hours per decade - this is
a whole workweek of just looking at the message and waiting for Godot.