diff options
author | Robin Haberkorn <robin.haberkorn@googlemail.com> | 2025-09-09 20:35:17 +0300 |
---|---|---|
committer | Robin Haberkorn <robin.haberkorn@googlemail.com> | 2025-09-09 20:45:38 +0300 |
commit | a673fe139a7cc44a7f2b4839aaa78124c49c4b75 (patch) | |
tree | 465827b560bc265d555c58069caff1d9a1376757 /.github | |
parent | 091695bad445c8931e9bd21e3a6ccfefac99657a (diff) | |
download | sciteco-a673fe139a7cc44a7f2b4839aaa78124c49c4b75.tar.gz |
work around ncurses mouse handling bugs
* We have to process several mouse events for every KEY_MOUSE.
* The order of events is sort of arbitrary after clicking the middle mouse button
in some terminal emulators like st and Xterm.
Therefore BUTTON2_PRESSED is now ignored and resynthesized when
receiving BUTTON2_RELEASED.
This fixes loosing middle click events.
fnkeys.tes only processes the RELEASED event anyway.
I am still looking for a fix to contribute to the ncurses project.
* In GNOME Terminal and Xterm with the SGR mouse protocol,
you can receive bogus BUTTON3_PRESSED events when left scrolling.
There is an upstream fix.
As a workaround -- we will have to live with outdated ncurses
versions anyway -- we prevent resetting the mouse mask unnecessarily.
This limits the effects to a single bogus BUTTON3_PRESSED event.
Unfortunately, it's not easily possible to force ncurses into using
the X10 mouse protocol even if the terminfo entry claims SGR compatibility.
See also https://lists.gnu.org/archive/html/bug-ncurses/2025-09/msg00016.html
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions