Ctrl+A, Ctrl+B, Ctrl+C etc. should always be handled as if the current KB layout were US English, at least for non-Latin layouts

[debushoukun]

The current behavior does not match the behavior of any other popular terminal app (Konsole, gnome-terminal, Kitty, iTerm2).

Steps to reproduce:

1. Open a shell in Ghostty.
2. Switch the keyboard layout to Russian, Greek or anything else that doesn't use the Latin alphabet.
3. Press Ctrl-C or Ctrl-D. Instead of the expected behavior, you'll see a bunch of escape sequences appear in the command line.

[vdrandom]

Do you have your Caps Lock remapped to ctrl? #4518 seems to have been fixed for the actual ctrl key, but not for the remapped ones.

[pluiedev]

I would assume OP is (also) on Linux since they mentioned Konsole and gnome-terminal, and I'm not aware if we've fully fixed this issue there.

[vdrandom]

They also mentioned iTerm2, which is very much not on Linux. :)

Regardless, I just wanted to make the issue more visible as it's the only reason I'm not using ghostty atm, would be great to make the switch one day.

[debushoukun]

The bug seems to have been fixed on macOS, but is still present on GNU/Linux.

[00-kat]

GNU/Linux

And all other Linux that Ghostty runs on, if any, presumably.

[mitchellh]

#7309

[pruge]

Still reproduces on Ghostty 1.3.1 (stable), macOS — so this doesn't appear to be fully fixed on macOS despite the pointer to #7309.

Repro

• Input source: Korean 2-Set (두벌식), toggled on — happens even when not mid-composition
• Press Ctrl+C → a literal J is inserted and no SIGINT reaches the foreground process
• Same breakage for other Ctrl+<letter> combos (Ctrl+A/E line editing, Ctrl+B as a tmux-style prefix, etc.)

Workaround — binding the physical keys fixes it completely, since physical keys are matched independent of layout/IME and outrank Unicode-codepoint triggers:

keybind = ctrl+key_c=text:\x03
keybind = ctrl+key_d=text:\x04
keybind = ctrl+key_z=text:\x1a
keybind = ctrl+key_a=text:\x01
keybind = ctrl+key_e=text:\x05

Worth noting: the logical binding keybind = ctrl+c=text:\x03 does not work here — it fails to match while the Korean input source is active. Only the physical ctrl+key_c form intercepts before the (mis)translation.