Files
ghostty/src
Mitchell Hashimoto fdfc9fea2f input: send composed text in kitty keyboard protocol
When the kitty keyboard protocol "report all keys as escape codes" mode
was active, composed/IME text (e.g. from dead keys or compose sequences)
was silently dropped. 

This happened because the composed text is sent within our GTK apprt
with key=unidentified and no unshifted_codepoint, so no kitty entry was
found and the encoder returned without producing any output. The
plain-text fallback was also skipped because report_all bypasses it.

Send composed text as raw UTF-8 when no kitty entry is found, matching
the behavior of Kitty on Linux for me.

Fixes #10049
2026-03-03 08:57:24 -08:00
..
2025-10-03 07:10:43 -07:00
2026-02-28 19:00:35 +11:00
2025-11-27 13:37:53 -08:00
2025-10-03 18:52:26 +02:00
2026-02-01 14:32:37 -08:00
2025-11-27 13:37:53 -08:00
2025-11-27 13:37:53 -08:00
2026-02-17 12:54:29 -06:00
2025-10-03 07:10:43 -07:00
2026-01-08 10:22:56 -08:00
2026-03-01 14:55:07 -08:00
2025-11-27 13:37:53 -08:00
2025-11-27 13:37:53 -08:00
2024-08-16 14:35:10 -07:00
2025-07-09 15:06:24 -07:00
2022-08-18 11:42:32 -07:00
2025-10-03 07:10:43 -07:00
2025-11-27 13:37:53 -08:00