Re: messages override minibuffer input

[Johannes Weiner]

Hi,

On Mon, Sep 10, 2007 at 02:41:26PM -0700, Davis Herring wrote:
> (defvar optional-message nil
>   "The last message shown with the function `optional-message'.")
> (defun optional-message (fmt &rest args)
>   "Display a message if there's nothing better being displayed."
>   (or (active-minibuffer-window)
>       (not (eq (current-message) optional-message))
>       (message "%s" (setq optional-message (apply 'format fmt args)))))

ELISP> (progn (setq foo "foo") (message foo) (eq (current-message) foo))
nil

This function calls `message' only when the minibuffer is active.  I am sorry,
I can not follow that logic.

How likely is it anyway that two EQUAL strings are messaged in a row?

        Hannes

signature.asc
Description: Digital signature