Terminal cannot process keystroke combinations with specific Win10 keyboard languages #7194

Open
opened 2026-01-31 00:57:30 +00:00 by claunia · 0 comments
Owner

Originally created by @mtjon on GitHub (Mar 29, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable):  0.10.781.0

wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-18.04    Running         2

Steps to reproduce

Set Windows 10 keyboard language to something that binds ctrl + alt + l, e.g.: English (United States International), which binds it to 'ø'.

Expected behavior

I expect the terminal to pick up the keystrokes as input, in my case it would be used as keybinding in my tmux configuration.

I would understand if this is classified as expected behaviour, but I'd much prefer Terminal to handle the keystrokes 'directly'.

Actual behavior

Windows sends the 'ø' to the Terminal, which does not know how to handle it, and displays it as <ffffffff>. My font (Fira Code) possibly doesn't contain the glyph.

Originally created by @mtjon on GitHub (Mar 29, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 0.10.781.0 wsl -l -v NAME STATE VERSION * Ubuntu-18.04 Running 2 ``` # Steps to reproduce Set Windows 10 keyboard language to something that binds `ctrl + alt + l`, e.g.: English (United States International), which binds it to 'ø'. # Expected behavior I expect the terminal to pick up the keystrokes as input, in my case it would be used as keybinding in my tmux configuration. I would understand if this is classified as expected behaviour, but I'd much prefer Terminal to handle the keystrokes 'directly'. # Actual behavior Windows sends the 'ø' to the Terminal, which does not know how to handle it, and displays it as `<ffffffff>`. My font (`Fira Code`) possibly doesn't contain the glyph.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7194