Ctrl+Alt+[arrow keys] are not working after update 1.2.2381.0 #10526

Closed
opened 2026-01-31 02:23:55 +00:00 by claunia · 8 comments
Owner

Originally created by @atifraza on GitHub (Sep 7, 2020).

Environment

Windows build number: 19041.450
Windows Terminal version (if applicable): 1.2.2381.0

Any other software?
WSL: 2
Distro: Ubuntu 20.04

Steps to reproduce

Keyboard layout: US (QWERTY) or US-International (QWERTY)

Terminal key bindings: default

"altGrAliasing": false

Expected behavior

Tmux in WSL has pane switching keybindings set to Ctrl+Alt+[arrow keys].
Before the update to 1.2.2381.0, the keybindings were working and switching panes in a window was possible with these keybindings.
Pressing Ctrl+Alt+[arrow keys] should be passed to the WSL instance so that tmux keybindings are triggered.

Actual behavior

After the update, the keybindings don't work anymore.
The "altGrAliasing": false setting has also been tested, and the checks as per pull request 7400 show the correct/expected characters.

Example:

$  showkey -a

Press any keys - Ctrl-D will terminate this program
# Pressed AltGr+Q
ä       195 0303 0xc3
        164 0244 0xa4
# Pressed Ctrl+Alt+Q
^[^Q     27 0033 0x1b
         17 0021 0x11
# Pressed AltGr+Q
ß       195 0303 0xc3
        159 0237 0x9f
# Pressed Ctrl+Alt+S
^[^S     27 0033 0x1b
         19 0023 0x13
Originally created by @atifraza on GitHub (Sep 7, 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: 19041.450 Windows Terminal version (if applicable): 1.2.2381.0 Any other software? WSL: 2 Distro: Ubuntu 20.04 ``` # Steps to reproduce Keyboard layout: US (QWERTY) or US-International (QWERTY) Terminal key bindings: default "altGrAliasing": false <!-- A description of how to trigger this bug. --> # Expected behavior Tmux in WSL has pane switching keybindings set to Ctrl+Alt+[arrow keys]. Before the update to 1.2.2381.0, the keybindings were working and switching panes in a window was possible with these keybindings. Pressing `Ctrl+Alt+[arrow keys]` should be passed to the WSL instance so that tmux keybindings are triggered. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior After the update, the keybindings don't work anymore. The `"altGrAliasing": false` setting has also been tested, and the checks as per pull request [7400](https://github.com/microsoft/terminal/pull/7400) show the correct/expected characters. Example: ```bash $ showkey -a Press any keys - Ctrl-D will terminate this program # Pressed AltGr+Q ä 195 0303 0xc3 164 0244 0xa4 # Pressed Ctrl+Alt+Q ^[^Q 27 0033 0x1b 17 0021 0x11 # Pressed AltGr+Q ß 195 0303 0xc3 159 0237 0x9f # Pressed Ctrl+Alt+S ^[^S 27 0033 0x1b 19 0023 0x13 ``` <!-- What's actually happening? -->
claunia added the Needs-TriageNeeds-Tag-FixResolution-No-Repro labels 2026-01-31 02:23:55 +00:00
Author
Owner

@atifraza commented on GitHub (Sep 10, 2020):

Something seems to have fixed the issue.

@atifraza commented on GitHub (Sep 10, 2020): Something seems to have fixed the issue.
Author
Owner

@DHowett commented on GitHub (Sep 10, 2020):

I hate bugs like that! Thanks for letting us know.

I'll reopen this if you comment and let me know that it's come back 😄

@DHowett commented on GitHub (Sep 10, 2020): I hate bugs like that! Thanks for letting us know. I'll reopen this if you comment and let me know that it's come back :smile:
Author
Owner

@dihmandrake commented on GitHub (Sep 15, 2020):

Edit: The issue has fixed itself for me as well. The only installed update on my machine is a new version of the WSL 2, but I doubt that had anything to do with this issue. Neither Windows or the Terminal was updated since then and I haven't changed the settings since the report of this issue. If it occours again I will update this comment.

I am seem to have the same issue. None of the shortcuts assigned to ctrl+alt+XY seem to work anymore. I am quite sure it used to work last week and it therefore might an issue with Windows, but I cannot guarantee that.

This might be releated to: https://github.com/microsoft/terminal/issues/7438

Terminal Version: Version: 1.2.2381.0
Windows Version: 10.0.19041.508

See the last few lines for examples.
Settings:

// This file was initially generated by Windows Terminal 0.11.1121.0
// It should still be usable in newer versions, but newer versions might have additional
// settings, help text, or changes that you will not see unless you clear this file
// and let us generate a new one for you.

// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation
{
    "$schema": "https://aka.ms/terminal-profiles-schema",

    "defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",

    // You can add more global application settings here.
    // To learn more about global settings, visit https://aka.ms/terminal-global-settings

    // If enabled, selections are automatically copied to your clipboard.
    "copyOnSelect": false,

    // If enabled, formatted data is also copied to your clipboard
    "copyFormatting": false,
    
    "alwaysShowTabs": false,

    // A profile specifies a command to execute paired with information about how it should look and feel.
    // Each one of them will appear in the 'New Tab' dropdown,
    //   and can be invoked from the commandline with `wt.exe -p xxx`
    // To learn more about profiles, visit https://aka.ms/terminal-profile-settings
    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles.
            "acrylicOpacity" : 0.9,
            "useAcrylic" : true,
            "background" : "#000000",
            "hidden": false
        },
        "list":
        [
            {
                // Make changes here to the powershell.exe profile.
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe"
            },
            {
                // Make changes here to the cmd.exe profile.
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "Command Prompt",
                "commandline": "cmd.exe"
            },
            {
                "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
                "name": "Ubuntu-20.04",
                "source": "Windows.Terminal.Wsl"
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure",
                "hidden": true
            }
        ]
    },

    // Add custom color schemes to this array.
    // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes
    "schemes": [],

    // Add custom keybindings to this array.
    // To unbind a key combination from your defaults.json, set the command to "unbound".
    // To learn more about keybindings, visit https://aka.ms/terminal-keybindings
    "actions":
    [
        // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json.
        // These two lines additionally bind them to Ctrl+C and Ctrl+V.
        // To learn more about selection, visit https://aka.ms/terminal-selection
        { "command": {"action": "copy", "singleLine": false }, "keys": "ctrl+c" },
        { "command": "paste", "keys": "ctrl+v" },

        // Press Ctrl+Shift+F to open the search box
        { "command": "find", "keys": "ctrl+shift+f" },

        // Press Alt+Shift+D to open a new pane.
        // - "split": "auto" makes this pane open in the direction that provides the most surface area.
        // - "splitMode": "duplicate" makes the new pane use the focused pane's profile.
        // To learn more about panes, visit https://aka.ms/terminal-panes
        { "command": { "action": "splitPane", "split": "auto", "splitMode": "duplicate" }, "keys": "ctrl+alt+d" },

        // These two settings do not work
        { "command": { "action": "splitPane", "split": "vertical" }, "keys": "ctrl+alt+right" },
        { "command": { "action": "splitPane", "split": "horizontal" }, "keys": "ctrl+alt+down" },

        { "command": "closePane", "keys": ["ctrl+alt+w"] }
    ]
}
@dihmandrake commented on GitHub (Sep 15, 2020): _Edit:_ The issue has fixed itself for me as well. The only installed update on my machine is a new version of the WSL 2, but I doubt that had anything to do with this issue. Neither Windows or the Terminal was updated since then and I haven't changed the settings since the report of this issue. If it occours again I will update this comment. I am seem to have the same issue. None of the shortcuts assigned to `ctrl+alt+XY` seem to work anymore. I am quite sure it used to work last week and it therefore might an issue with Windows, but I cannot guarantee that. This might be releated to: https://github.com/microsoft/terminal/issues/7438 Terminal Version: Version: `1.2.2381.0` Windows Version: `10.0.19041.508` See the last few lines for examples. Settings: ```json // This file was initially generated by Windows Terminal 0.11.1121.0 // It should still be usable in newer versions, but newer versions might have additional // settings, help text, or changes that you will not see unless you clear this file // and let us generate a new one for you. // To view the default settings, hold "alt" while clicking on the "Settings" button. // For documentation on these settings, see: https://aka.ms/terminal-documentation { "$schema": "https://aka.ms/terminal-profiles-schema", "defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", // You can add more global application settings here. // To learn more about global settings, visit https://aka.ms/terminal-global-settings // If enabled, selections are automatically copied to your clipboard. "copyOnSelect": false, // If enabled, formatted data is also copied to your clipboard "copyFormatting": false, "alwaysShowTabs": false, // A profile specifies a command to execute paired with information about how it should look and feel. // Each one of them will appear in the 'New Tab' dropdown, // and can be invoked from the commandline with `wt.exe -p xxx` // To learn more about profiles, visit https://aka.ms/terminal-profile-settings "profiles": { "defaults": { // Put settings here that you want to apply to all profiles. "acrylicOpacity" : 0.9, "useAcrylic" : true, "background" : "#000000", "hidden": false }, "list": [ { // Make changes here to the powershell.exe profile. "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name": "Windows PowerShell", "commandline": "powershell.exe" }, { // Make changes here to the cmd.exe profile. "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "name": "Command Prompt", "commandline": "cmd.exe" }, { "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}", "name": "Ubuntu-20.04", "source": "Windows.Terminal.Wsl" }, { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure", "hidden": true } ] }, // Add custom color schemes to this array. // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes "schemes": [], // Add custom keybindings to this array. // To unbind a key combination from your defaults.json, set the command to "unbound". // To learn more about keybindings, visit https://aka.ms/terminal-keybindings "actions": [ // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json. // These two lines additionally bind them to Ctrl+C and Ctrl+V. // To learn more about selection, visit https://aka.ms/terminal-selection { "command": {"action": "copy", "singleLine": false }, "keys": "ctrl+c" }, { "command": "paste", "keys": "ctrl+v" }, // Press Ctrl+Shift+F to open the search box { "command": "find", "keys": "ctrl+shift+f" }, // Press Alt+Shift+D to open a new pane. // - "split": "auto" makes this pane open in the direction that provides the most surface area. // - "splitMode": "duplicate" makes the new pane use the focused pane's profile. // To learn more about panes, visit https://aka.ms/terminal-panes { "command": { "action": "splitPane", "split": "auto", "splitMode": "duplicate" }, "keys": "ctrl+alt+d" }, // These two settings do not work { "command": { "action": "splitPane", "split": "vertical" }, "keys": "ctrl+alt+right" }, { "command": { "action": "splitPane", "split": "horizontal" }, "keys": "ctrl+alt+down" }, { "command": "closePane", "keys": ["ctrl+alt+w"] } ] } ```
Author
Owner

@dihmandrake commented on GitHub (Sep 24, 2020):

For anyone that might stumble upon this issue: I finally figured out what caused the problem on my machine. Intel Graphics Command Center. Even though Hotkeys are disabled they sometimes block the keyboard combinations with crtl+alt in applications. Enabling and disabling the combinations in the Intel Graphics Command Center solves the issue for me. Still, it appears that the Intel implementation contains some bugs and they block combinations after a while (might be reboot releated).

image

@dihmandrake commented on GitHub (Sep 24, 2020): For anyone that might stumble upon this issue: I finally figured out what caused the problem on my machine. Intel Graphics Command Center. Even though Hotkeys are disabled they sometimes block the keyboard combinations with `crtl+alt` in applications. Enabling and disabling the combinations in the Intel Graphics Command Center solves the issue for me. Still, it appears that the Intel implementation contains some bugs and they block combinations after a while (might be reboot releated). ![image](https://user-images.githubusercontent.com/16025288/94138568-9babc180-fe68-11ea-8627-959d8d3601a8.png)
Author
Owner

@Edstar3000 commented on GitHub (Aug 28, 2022):

what about shift+ arrow keys? output is a d in wsl2
very frustrating to needing the mouse in this context

@Edstar3000 commented on GitHub (Aug 28, 2022): what about shift+ arrow keys? output is a d in wsl2 very frustrating to needing the mouse in this context
Author
Owner

@zadjii-msft commented on GitHub (Aug 29, 2022):

@Edstar3000 first off, this thread is like two years old and totally unrelated to shift+arrows selection. You're probably interested in "Mark mode", which I believe shipped in 1.15 builds.

@zadjii-msft commented on GitHub (Aug 29, 2022): @Edstar3000 first off, this thread is like two years old and totally unrelated to shift+arrows selection. You're probably interested in ["Mark mode"](https://docs.microsoft.com/en-us/windows/terminal/selection#keyboard-support), which I believe shipped in 1.15 builds.
Author
Owner

@Edstar3000 commented on GitHub (Aug 29, 2022):

Damn this was fast.
Thanks a lot!
However, I still cannot mark words by using shift + arrow keys as it is
easily done with Linux.
On the thread stated above I could not find a solution either, am I stupid?

Mit freundlichen Grüßen

Edgar Kretschmann

@Edstar3000 commented on GitHub (Aug 29, 2022): Damn this was fast. Thanks a lot! However, I still cannot mark words by using shift + arrow keys as it is easily done with Linux. On the thread stated above I could not find a solution either, am I stupid? Mit freundlichen Grüßen Edgar Kretschmann
Author
Owner

@zadjii-msft commented on GitHub (Aug 29, 2022):

@Edstar3000 Try binding

        {
            "command": "markMode",
            "keys": "shift+left"
        },

in the settings.

dfb022fb-4dfc-4fbd-b7e4-22ba739604b2

@zadjii-msft commented on GitHub (Aug 29, 2022): @Edstar3000 Try binding ```json { "command": "markMode", "keys": "shift+left" }, ``` in the settings. ![dfb022fb-4dfc-4fbd-b7e4-22ba739604b2](https://user-images.githubusercontent.com/18356694/187252911-4241e257-9403-4394-91d4-dac814bd0fd3.gif)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10526