Re: Q on minibuffer-message

[Eli Zaretskii]

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Sun, 22 Jan 2006 10:54:35 -0800
> Cc: 
> 
>     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.
> 
> That's just what I wanted to avoid having to do. From my original message:
> 
>     I could change the definition of command `foo', to pass it a flag to not
>     call `minibuffer-message' (or to call it only when the command is called
>     interactively), but I'd rather not have to resort to that.

This doesn't explain why you wanted to avoid such a solution.