From d885a266d4c513a97121f1467d4cbe9c453da6bc Mon Sep 17 00:00:00 2001 From: Sam Atman Date: Thu, 19 Dec 2024 16:51:28 -0500 Subject: [PATCH] Docfix: correct comment for modifyOtherKeys sequence The comment in `function_keys.zig` was missing the `>` character for the sequence. I've confirmed that this was just the comment, Ghostty treats the original as an SGR sequence, which it is. Conversely, it does treat `\x1b[>4:2m` as activating modifyOtherKeys. --- src/input/function_keys.zig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/input/function_keys.zig b/src/input/function_keys.zig index 2a54ba12a..61af5b037 100644 --- a/src/input/function_keys.zig +++ b/src/input/function_keys.zig @@ -13,7 +13,7 @@ pub const CursorMode = enum { any, normal, application }; pub const KeypadMode = enum { any, normal, application }; /// A bit confusing so I'll document this one: this is the "modify other keys" -/// setting. We only change behavior for "set_other" which is ESC [ 4; 2 m. +/// setting. We only change behavior for "set_other" which is ESC [ > 4; 2 m. /// So this can be "any" which means we don't care what's going on. Or it /// can be "set" which means modify keys must be set EXCEPT FOR "other keys" /// mode, and "set_other" which means modify keys must be set to "other keys"