[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Q on minibuffer-message
From: |
Ian Zimmerman |
Subject: |
Re: Q on minibuffer-message |
Date: |
Sun, 22 Jan 2006 21:11:23 -0800 (PST) |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 |
rms> In that case, what I suggest is that you set up foo with an
rms> optional argument that is provided as t when it is called
rms> interactively. And foo should only display its messages when that
rms> argument is t.
Drew> That's just what I wanted to avoid having to do. From my original
Drew> message:
Drew> I could change the definition of command `foo', to pass it a
Drew> flag to not call `minibuffer-message' (or to call it only when the
Drew> command is called interactively), but I'd rather not have to
Drew> resort to that.
But why? The argument can be optional, meaning if it's not given it will
default to nil. So there's no need to modify call sites in programs.
--
A true pessimist won't be discouraged by a little success.
- 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, 2006/01/22
- 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 <=
- 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