[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: messages override minibuffer input
From: |
Davis Herring |
Subject: |
Re: messages override minibuffer input |
Date: |
Wed, 12 Sep 2007 09:25:50 -0700 (PDT) |
User-agent: |
SquirrelMail/1.4.8-6.el3.2lanl |
> 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.