[Bug]: Hotkeys work only with English keyboard layout #2189

Activity

1. Ask1n

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.

   on Apr 18, 2026
2. YakovL commented on Jun 5, 2026

   

   YakovL

   on Jun 5, 2026

   Last edited by YakovL

   More actions

   Having same issue (for instance, ctrl+j doesn't work when not in English layout).

   Probable culprit: usage of event.key instead of event.code here (well, the next line checkes event.code, but EVENT_CODE_KEY_ALIASES doesn't have KeyJ: ["j"] anyway).

   A minimal (although not a beautiful) fix would probably be adding this to EVENT_CODE_KEY_ALIASES:

   KeyA: ["a"], KeyB: ["b"], KeyC: ["c"], KeyD: ["d"], KeyE: ["e"],
   KeyF: ["f"], KeyG: ["g"], KeyH: ["h"], KeyI: ["i"], KeyJ: ["j"],
   KeyK: ["k"], KeyL: ["l"], KeyM: ["m"], KeyN: ["n"], KeyO: ["o"],
   KeyP: ["p"], KeyQ: ["q"], KeyR: ["r"], KeyS: ["s"], KeyT: ["t"],
   KeyU: ["u"], KeyV: ["v"], KeyW: ["w"], KeyX: ["x"], KeyY: ["y"],
   KeyZ: ["z"],
   
3. juliusmarminge commented on Jun 20, 2026

   

   juliusmarminge

   on Jun 20, 2026 – with ChatGPT Codex Connector

   Member

   More actions

   Keyboard shortcut resolution now maps physical KeyA–KeyZ codes in addition to layout-derived keys, with regression coverage for layout-modified shortcuts. This addresses the English-layout-only behavior.

   This was closed as part of a large repo-wide maintenance sweep. If you think it's still relevant, please reopen.
4. juliusmarminge

   closed this as completedon Jun 20, 2026