[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: messages override minibuffer input
From: |
Roland Winkler |
Subject: |
Re: messages override minibuffer input |
Date: |
Mon, 17 Sep 2007 16:49:08 +0200 |
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
- messages override minibuffer input, Roland Winkler, 2007/09/08
- Re: messages override minibuffer input, Stefan Monnier, 2007/09/08
- Re: messages override minibuffer input, Richard Stallman, 2007/09/08
- Re: messages override minibuffer input, Roland Winkler, 2007/09/15
- Re: messages override minibuffer input, Richard Stallman, 2007/09/16
- Re: messages override minibuffer input,
Roland Winkler <=
- Re: messages override minibuffer input, Richard Stallman, 2007/09/17
- Re: messages override minibuffer input, Roland Winkler, 2007/09/22
- Re: messages override minibuffer input, Richard Stallman, 2007/09/23
- Re: messages override minibuffer input, Roland Winkler, 2007/09/23
- Re: messages override minibuffer input, Richard Stallman, 2007/09/23
- Re: messages override minibuffer input, Roland Winkler, 2007/09/23
- Re: messages override minibuffer input, Richard Stallman, 2007/09/24
- Re: messages override minibuffer input, Roland Winkler, 2007/09/24
- RE: messages override minibuffer input, Drew Adams, 2007/09/23
- RE: messages override minibuffer input, Roland Winkler, 2007/09/23