Re: messages override minibuffer input

[Roland Winkler]

On Sun Sep 16 2007 Richard Stallman wrote:
>     If I understand the code correctly, the function do_autoload in
>     eval.c normally calls load with arg NOMESSAGE being nil. So load
>     issues a message. Would it make sense that load used something like
>     optional-message?
> 
> That change goes too far.  In the case you describe, do_autoload
> should not display the message.  But in many other cases it should.

Would it be better to do what Stefan proposed in a previous post?

  Another way to do it is to make such async-messages appear *after*
  the current minibuffer's content (typically enclosed on backets,
  as is done for completion messages).

Roland