starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

ctrl+alt+[arrow key] custom keybindings do not seem to be bound #8966

New Issue
Closed
opened 2026-01-31 01:42:35 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 01:42:35 +00:00
Owner
Copy Link

Originally created by @Q-Mart on GitHub (Jun 11, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.836]
Windows Terminal version (if applicable): 1.0.1401.0

Any other software?

Steps to reproduce

From a default terminal settings.json file, insert the following lines into the keybindings array:

{ "command": "unbound", "keys": [ "alt+down" ]},
{ "command": "unbound", "keys": [ "alt+left" ]},
{ "command": "unbound", "keys": [ "alt+right" ]},
{ "command": "unbound", "keys": [ "alt+up" ]},

{ "command": { "action": "moveFocus", "direction": "down" }, "keys": "ctrl+alt+down" },
{ "command": { "action": "moveFocus", "direction": "left" }, "keys": "ctrl+alt+left" },
{ "command": { "action": "moveFocus", "direction": "right" }, "keys": "ctrl+alt+right" },
{ "command": { "action": "moveFocus", "direction": "up" }, "keys": "ctrl+alt+up" }

Then, open an instance of Windows Terminal (or go to a running instance if you already have it open) and split some panes. Use ctrl+alt+[arrow keys] to move between the panes

Expected behavior

You should moving focus between panes, in the direction of the arrow key pressed (along with ctrl and alt).

Actual behavior

Nothing, your focus remains on the pane you were already focused on.

Originally created by @Q-Mart on GitHub (Jun 11, 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: Microsoft Windows [Version 10.0.18363.836] Windows Terminal version (if applicable): 1.0.1401.0 Any other software? ``` # Steps to reproduce From a default terminal `settings.json` file, insert the following lines into the `keybindings `array: ``` { "command": "unbound", "keys": [ "alt+down" ]}, { "command": "unbound", "keys": [ "alt+left" ]}, { "command": "unbound", "keys": [ "alt+right" ]}, { "command": "unbound", "keys": [ "alt+up" ]}, { "command": { "action": "moveFocus", "direction": "down" }, "keys": "ctrl+alt+down" }, { "command": { "action": "moveFocus", "direction": "left" }, "keys": "ctrl+alt+left" }, { "command": { "action": "moveFocus", "direction": "right" }, "keys": "ctrl+alt+right" }, { "command": { "action": "moveFocus", "direction": "up" }, "keys": "ctrl+alt+up" } ``` Then, open an instance of Windows Terminal (or go to a running instance if you already have it open) and split some panes. Use `ctrl+alt+[arrow keys] ` to move between the panes # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> You should moving focus between panes, in the direction of the arrow key pressed (along with ctrl and alt). # Actual behavior <!-- What's actually happening? --> Nothing, your focus remains on the pane you were already focused on.
claunia commented 2026-01-31 01:42:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 11, 2020):

(I'm assuming that the missing }, at the end of the first four lines was uninitentional, and in your actual settings.json the lines are correct)

Well that's weird. I can't seem to repro this locally.

What keyboard layout are you using? Are you using any IME's?

As an experiment, does binding any of the following keys work?

  • alt+up
  • ctrl+up
  • ctrl+alt+up
  • alt+p (the p is arbitrary, I just wanted a key that's also definitely a character)
  • ctrl+p
  • ctrl+alt+p
@zadjii-msft commented on GitHub (Jun 11, 2020): _(I'm assuming that the missing ` },` at the end of the first four lines was uninitentional, and in your actual `settings.json` the lines are correct)_ Well that's weird. I can't seem to repro this locally. What keyboard layout are you using? Are you using any IME's? As an experiment, does binding any of the following keys work? * `alt+up` * `ctrl+up` * `ctrl+alt+up` * `alt+p` (the `p` is arbitrary, I just wanted a key that's also definitely a character) * `ctrl+p` * `ctrl+alt+p`
claunia commented 2026-01-31 01:42:36 +00:00
Author
Owner
Copy Link

@Q-Mart commented on GitHub (Jun 11, 2020):

(I'm assuming that the missing }, at the end of the first four lines was uninitentional, and in your actual settings.json the lines are correct)
You are correct, sorry. I've edited the comment to remove this error

What keyboard layout are you using? Are you using any IME's?
English GB QWERTY layout, no IMEs.

Here are the results of the keybindings you asked for (✔️ means it worked, ❌ means it didn't):

  • alt+up ✔️
  • ctrl+up ✔️
  • ctrl+alt+up ❌
  • alt+p ✔️
  • ctrl+p ✔️
  • ctrl+alt+p ❌

One thing I forgot to mention in the original comment (because, honestly I just forgot I was in one) is that I'm using the terminal over a remote desktop connection. It seems that RDP keyboard shortcuts begin with ctrl+alt (source) so I assume the reason ctrl+alt shortcuts aren't being picked up is because RDP is fiddling with something?

@Q-Mart commented on GitHub (Jun 11, 2020): > (I'm assuming that the missing }, at the end of the first four lines was uninitentional, and in your actual settings.json the lines are correct) You are correct, sorry. I've edited the comment to remove this error > What keyboard layout are you using? Are you using any IME's? English GB QWERTY layout, no IMEs. Here are the results of the keybindings you asked for (✔️ means it worked, ❌ means it didn't): - `alt+up` ✔️ - `ctrl+up` ✔️ - `ctrl+alt+up` ❌ - `alt+p` ✔️ - `ctrl+p` ✔️ - `ctrl+alt+p` ❌ One thing I forgot to mention in the original comment (because, honestly I just forgot I was in one) is that I'm using the terminal over a remote desktop connection. It seems that RDP keyboard shortcuts begin with `ctrl+alt` ([source](https://docs.microsoft.com/en-us/windows/win32/termserv/terminal-services-shortcut-keys)) so I assume the reason `ctrl+alt` shortcuts aren't being picked up is because RDP is fiddling with something?
claunia commented 2026-01-31 01:42:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 17, 2020):

Actually... does your keyboard have an AltGr key?

@DHowett commented on GitHub (Jun 17, 2020): Actually... does your keyboard have an `AltGr` key?
claunia commented 2026-01-31 01:42:36 +00:00
Author
Owner
Copy Link

@Q-Mart commented on GitHub (Jun 17, 2020):

Yes

@Q-Mart commented on GitHub (Jun 17, 2020): Yes
claunia commented 2026-01-31 01:42:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 19, 2020):

Ah, that'll do it. The Terminal is treating Ctlr+alt as the same thing as AltGr. I think you can disable this behavior with "altGrAliasing": false - does that change anything?

@zadjii-msft commented on GitHub (Jun 19, 2020): Ah, that'll do it. The Terminal is treating <kbd>Ctlr+alt</kbd> as the same thing as <kbd>AltGr</kbd>. I think you can disable this behavior with `"altGrAliasing": false` - does that change anything?
claunia commented 2026-01-31 01:42:37 +00:00
Author
Owner
Copy Link

@Q-Mart commented on GitHub (Jun 22, 2020):

Aha, I don't think I'm able to test this at the moment as the the altGrAliasing setting is only in the preview (which I am not using)

@Q-Mart commented on GitHub (Jun 22, 2020): Aha, I don't think I'm able to test this at the moment as the the `altGrAliasing` setting is only in the preview (which I am not using)
claunia commented 2026-01-31 01:42:37 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 27, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 27, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8966
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?