Re: `y-or-n-p' does not wait for input - assumes `n'

[Stefan Monnier]

>     The problem is normally shifted elsewhere: make sure you don't put
>     bindings like that on a down-mouse-N key but on a mouse-N key instead.
> Shouldn't buttons act on the down event, not the up event?

No, for the exact reason discussed here: if they act on the down event, the
following up-event might be executed in a state which the user hasn't seen
yet (because the button's action is to switch to some other buffer, for
example).  A typical example is a "back" or "quit" button: if it acts on
the down event (and is fast enough), the user has the impression that the
button disappeared right when he clicked, like "fleeing button".

Also as I user I sometimes do "down....[oops-no-I-didn't-mean-that]..move
away...up" when I realize midcourse that it wasn't what I wanted to do.


        Stefan