diff options
author | robert <robertrussell.72001@gmail.com> | 2022-01-08 11:40:34 -0800 |
---|---|---|
committer | Gustaf Rydholm <gustaf.rydholm@gmail.com> | 2023-05-08 00:36:09 +0200 |
commit | f7bde7d8f55ffcf86128e497d7850c2f386721e4 (patch) | |
tree | 41ccb936e82f1f3d966462c686cc4e6f705da949 /patches/st-bold-is-not-bright-20190127-3be4cf1.diff | |
parent | daae1b5d4ee81ceb84bf3eddc0290bc14dc5b8d9 (diff) |
Fix mousereport
This patch replaces the previous one I sent.
The following changes are made in this patch:
- Fix tracking of pressed buttons. Previously, pressing two buttons and
then releasing one would make st think no buttons are pressed, which
in particular broke MODE_MOUSEMOTION.
- Always send the lowest-numbered pressed button on motion events; when
no button is pressed for a motion event in MODE_MOUSEMANY, then send
a release. This matches the behaviour of xterm. (Previously, st sent
the most recently pressed button in the motion report.)
- Remove UB (?) access to potentially inactive struct member
e->xbutton.button of XEvent union.
- Fix (unlikely) possibility of overflow for large button numbers.
The one discrepancy I found between st and xterm is that xterm sometimes
encodes buttons with large numbers (>5) strangely. E.g., xterm reports
presses of buttons 8 and 9 as releases, whereas st properly (?) encodes
them as presses.
Diffstat (limited to 'patches/st-bold-is-not-bright-20190127-3be4cf1.diff')
0 files changed, 0 insertions, 0 deletions