Re: messages override minibuffer input

[Davis Herring]

> Whoops, got it backwards.  The call to `message' happens only when the
> minibuffer is inactive.  But anyway, the second argument to `or' still
> seems
> useless to me, because `current-message' returns a new string object.

It is; I thought one could use eq here, but it seems equal is required. 
Which is not as good: a stream of unimportant messages could then proceed
if the first of them happened to duplicate an important message.  I guess
we could stick an "unimportant" property on unimportant messages and then
compare them with `equal-including-properties'.

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.