[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Q on minibuffer-message
From: |
Richard M. Stallman |
Subject: |
Re: Q on minibuffer-message |
Date: |
Sun, 22 Jan 2006 12:44:57 -0500 |
> I have a command `foo' that calls `minibuffer-message' at various points.
>
> I want to call this function from another command, `bar', but I don't want
> the `minibuffer-message' display to wait for two seconds - I even don't
care
> if it is displayed at all in this case.
It is not useful to display a minibuffer message and not wait to give
the user a chance to see it. The operation must normally wait.
Perhaps what you mean is that when foo is used from bar,
you see no reason for foo's messages to appear at all.
In that case, what I suggest is that you set up foo with an optional
argument that is provided as t when it is called interactively. And
foo should only display its messages when that argument is t.
- Q on minibuffer-message, Drew Adams, 2006/01/20
- Re: Q on minibuffer-message, Lennart Borgman, 2006/01/20
- RE: Q on minibuffer-message, Drew Adams, 2006/01/20
- Re: Q on minibuffer-message,
Richard M. Stallman <=
- RE: Q on minibuffer-message, Drew Adams, 2006/01/22
- Re: Q on minibuffer-message, Eli Zaretskii, 2006/01/22
- Re: Q on minibuffer-message, Ian Zimmerman, 2006/01/23
- RE: Q on minibuffer-message, Drew Adams, 2006/01/23
- Re: Q on minibuffer-message, Eli Zaretskii, 2006/01/23
- RE: Q on minibuffer-message, Drew Adams, 2006/01/23
- Re: Q on minibuffer-message, Eli Zaretskii, 2006/01/23
- Re: Q on minibuffer-message, Richard M. Stallman, 2006/01/24