bug#19718: read_filtered_event echos mouse events until character is inputted

[Lars Ingebrigtsen <larsi@gnus.org>]

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

Nick Andryshak <nandryshak@gmail.com> writes:

> See this Stack Exchange question: 
>
> http://emacs.stackexchange.com/questions/7443/mouse-problem-in-org-mode-export-window
>
> The asker is trying to use the mouse wheel to scroll the
> org-export-dispatch window. org-export-dispatch is using the built-in
> function read-char-exclusive, which in turn calls read_filtered_event
> with the parameter error_nonascii set to 0. Unlike read-char, which
> will throw an error upon receiving a mouse event, read-char-exclusive
> just keeps retrying, and eventually the echo area will become full of
> mouse event names.

Yes, I've always wondered what the point of that was.  Test case:

M-: (read-char-exclusive "foo: ")
<mouse-1>

After waiting a bit, the echo area will say:


[-- Attachment #2: down.jpg --]
[-- Type: image/jpeg, Size: 8644 bytes --]

[-- Attachment #3: Type: text/plain, Size: 193 bytes --]


I don't really see the point of that?  Are there any circumstances that
this is useful?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no