[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: messages override minibuffer input
From: |
Richard Stallman |
Subject: |
Re: messages override minibuffer input |
Date: |
Sun, 16 Sep 2007 20:20:27 -0400 |
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.
Perhaps do_autoload, when called from a timer, should not display the
message. But it should put the message in *Messages*.
Ideally it should display the message, but restore the previous echo
area contents later. The hard part of that is arranging for the
proper "later" time.
- 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 <=
- Re: messages override minibuffer input, Roland Winkler, 2007/09/17
- 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