diff options
| author | Stefan Monnier | 2019-05-10 08:49:03 -0400 |
|---|---|---|
| committer | Stefan Monnier | 2019-05-10 08:51:39 -0400 |
| commit | 655634808ad3b324ab844c53006e648b45713364 (patch) | |
| tree | 3b009d61839bf3b0a86db1c0f3110fc7f47dcdcf /src/alloc.c | |
| parent | e8709e790006c75e1c91dbf0d50d5dbc816329f6 (diff) | |
| download | emacs-655634808ad3b324ab844c53006e648b45713364.tar.gz emacs-655634808ad3b324ab844c53006e648b45713364.zip | |
* lisp/help.el (help--read-key-sequence): Handle `switch-frame' events
If you do `C-h k ... mouse-1 in other frame` (at least if you have a focus
that follows the mouse), then additionally to the down-mouse-1 and mouse-1
events, a `switch-frame` event (and `select-window` event as well sometimes)
is generated. When `read-key-sequence` is called with nil for
`can-return-switch-frame`, this event is not returned but kept for later,
which causes a subsequent `sit-for` to return nil immediately.
This interfered without our "wait for double-click" which in turn prevented
us from stopping after the mouse-1 click, getting stuck waiting for something
else instead.
(help--read-key-sequence): Pass a non-nil `can-return-switch-frame`, so the
subsequent `sit-for` returns more trustworthy information.
Diffstat (limited to 'src/alloc.c')
0 files changed, 0 insertions, 0 deletions