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

[Stefan Monnier]

>     Wouldn't it be better to fix this in C code so other potential uses of
>     y-or-n-p and yes-or-no-p during track-mouse do not need to be fixed
>     as well ?

> I think that the right solution in this case is for the
> specific callers to avoid calling them inside
> of track-mouse.

I disagree.  The problem is actually not limited to mouse-movement.
There's also switch-frame and select-window.

>     The problem is that `track-mouse' not only messes up y-or-n-p and
>     yes-or-no-p.  It messes up all functions that are trying to read user
>     input without wanting to track mouse motion.

> Some kinds of input might ignore the mouse motion events, but
> basically you are right.  However, I think the main solution should be
> to limit the part of the code that is inside the track-mouse binding,
> so that it doesn't affect other activities.

Most code that uses things like read-event end up looping and filtering
unwanted events.  See the recent issue with mouse-drag-region and
mouse-autoselect-window, which I ended up solving by adding select-window to
the ignored events.


        Stefan