aboutsummaryrefslogtreecommitdiff
path: root/server.c
diff options
context:
space:
mode:
authorDaniel Eklöf <daniel@ekloef.se>2025-01-20 08:08:47 +0000
committerDaniel Eklöf <daniel@ekloef.se>2025-01-20 08:08:47 +0000
commit2ff38e86a7fabd8fd90caa31c7eb0aea76fc981b (patch)
tree7c22c412bd250602fbff6fddbc8a817b6b728d88 /server.c
parentvt: combining chars: ensure 'key' is within range (diff)
input: kitty: fix alternate codepoint sometimes not being reported
When alternate key reporting is enabled (i.e. when we're supposed to report the shifted key along with the unshifted key), we try to figure out whether the key really is shifted or not (and thus which xkb keysym to use for the unshifted and shifted keys in the escape). This was done by getting the layout's *all* modifier combinations that produce the shifted keysym, and if any of of them contained a modifier that isn't supported by the kitty protocol, the shifted and unshifted keys are derived from the same keysym. This is to ensure we handle things like AltGr-combos correctly. The issue is, since there may be more than one modifier combination generating the shifted keysym, we may end up using the wrong keysym just because _another_ combination set contains modifiers not supported by the kitty protocol. What we're interrested in is whether the *pressed* set of modifiers contains such modifiers. Closes #1918
Diffstat (limited to 'server.c')
0 files changed, 0 insertions, 0 deletions