diff options
| author | Daniel Eklöf <daniel@ekloef.se> | 2022-07-26 16:44:29 +0000 |
|---|---|---|
| committer | Daniel Eklöf <daniel@ekloef.se> | 2022-07-28 17:02:25 +0000 |
| commit | 801970aa332da5786f91d2f9410d4ed9f440c6ec (patch) | |
| tree | 002fb5ebc3139141746830e9425cf594889fd62a /input.c | |
| parent | keymap: change alt+escape to emit \E\E instead of a CSI 27 sequence (diff) | |
input: kitty: always treat composed characters as ‘printable’
Certain dead key combinations results different escape sequences in
foot, compared to kitty, when the kitty keyboard protocol is used.
if (composed && is_text)
key = utf32;
else {
key = xkb_keysym_to_utf32(sym_to_use);
if (key == 0)
return false;
/* The *shifted* key. May be the same as the unshifted
* key - if so, this is filtered out below, when
* emitting the CSI */
alternate = xkb_keysym_to_utf32(sym);
}
If is_text=false, we’ll fall through to the non-composed
logic. is_text is set to true if the character is printable *and*
there aren’t any non-consumed modifiers enabled.
shift+space is one example where shift is *not* consumed (typically -
may be layouts where it is).
As a result, pressing ", followed by shift+space with the
international english keyboard layout (where " is a dead key) results
in different sequences in foot and kitty.
This patch fixes this by always treating composed characters as
printable.
Closes #1120
Diffstat (limited to 'input.c')
| -rw-r--r-- | input.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1239,7 +1239,7 @@ emit_escapes: ? ctx->level0_syms.syms[0] : sym; - if (composed && is_text) + if (composed) key = utf32; else { key = xkb_keysym_to_utf32(sym_to_use); |
