Re: Q on minibuffer-message

[Ian Zimmerman]

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.