Re: minibuffer-message binds inhibit-quit

[Eli Zaretskii]

> From: "Drew Adams" <address@hidden>
> Date: Tue, 24 Jun 2008 13:52:01 -0700
> 
> This let binding was recently added to `minibuffer-message':
> 
> ;; A quit during sit-for normally only interrupts the sit-for,
> ;; but since minibuffer-message is used at the end of a command,
> ;; at a time when the command has virtually finished already, a C-g
> ;; should really cause an abort-recursive-edit instead (i.e. as if
> ;; the C-g had been typed at top-level).  Binding inhibit-quit here
> ;; is an attempt to get that behavior.
> (inhibit-quit t)
> 
> I don't know about the effects of the binding (can't check until I get a more
> recent Windows build) - perhaps this change is appropriate. But if it requires
> the assumption stated in the comment, then it is not appropriate.
> 
> The assumption is invalid - it is by no means necessarily true that
> "minibuffer-message is used at the end of a command, at a time when the 
> command
> has virtually finished already".
> 
> `minibuffer-message' should be for messages during minibuffer input - that's
> all. Nothing should be assumed about when the command that calls it might be
> ended or is "virtually finished". 

Are you sure you are not confusing minibuffer with the echo area?  The
minibuffer and `minibuffer-message' are not normally used for messages
during minibuffer input; that's what the echo area is for.