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

Alt+ key combinations not being registered #20110

New Issue
Closed
opened 2026-01-31 07:03:48 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:03:48 +00:00
Owner
Copy Link

Originally created by @lszinv on GitHub (Jun 19, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.22621.1848

Other Software

No response

Steps to reproduce

All interactions using the Alt key are behaving as if the Alt key wasn't pressed. I was previously on Windows 10 and the version of Windows Terminal was behaving fine, but I just updated to Windows 11 and can no longer send the Alt key to the terminal. I've tried changing the AltGR aliasing option to no avail.

I've also gone and removed all existing shortcuts that included Alt as a key from Settings>Actions

For example in bash:
alt+b / alt+f to move cursor backwards/forwards words

Expected Behavior

Expected behaviour when passing in alt+b should move backwards by a word, and alt+f should move forwards by a word

Actual Behavior

Alt+b just inputs b into the CLI
Alt+f does nothing. Seems to be getting captured elsewhere

The desired behaviour works if I use ctrl+[ instead of Alt.

Originally created by @lszinv on GitHub (Jun 19, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.22621.1848 ### Other Software _No response_ ### Steps to reproduce All interactions using the Alt key are behaving as if the Alt key wasn't pressed. I was previously on Windows 10 and the version of Windows Terminal was behaving fine, but I just updated to Windows 11 and can no longer send the Alt key to the terminal. I've tried changing the AltGR aliasing option to no avail. I've also gone and removed all existing shortcuts that included Alt as a key from Settings>Actions For example in bash: alt+b / alt+f to move cursor backwards/forwards words ### Expected Behavior Expected behaviour when passing in alt+b should move backwards by a word, and alt+f should move forwards by a word ### Actual Behavior Alt+b just inputs b into the CLI Alt+f does nothing. Seems to be getting captured elsewhere The desired behaviour works if I use `ctrl+[` instead of Alt.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:03:48 +00:00
claunia commented 2026-01-31 07:03:49 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 19, 2023):

This works fine for me on Windows 11 with Windows Terminal 1.17. What keyboard layout are you using? Can you install showkey and run it as showkey -a? If you press a key like Alt+B it should show this:

^[b      27 0033 0x1b
         98 0142 0x62
@lhecker commented on GitHub (Jun 19, 2023): This works fine for me on Windows 11 with Windows Terminal 1.17. What keyboard layout are you using? Can you install `showkey` and run it as `showkey -a`? If you press a key like Alt+B it should show this: ``` ^[b 27 0033 0x1b 98 0142 0x62 ```
claunia commented 2026-01-31 07:03:49 +00:00
Author
Owner
Copy Link

@lszinv commented on GitHub (Jun 19, 2023):

Turns out my keyboard was faulty. I reflashed my fw on it and the issue went away.

@lszinv commented on GitHub (Jun 19, 2023): Turns out my keyboard was faulty. I reflashed my fw on it and the issue went away.
claunia commented 2026-01-31 07:03:49 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 19, 2023):

Thanks for letting us know!

@DHowett commented on GitHub (Jun 19, 2023): Thanks for letting us know!
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 Issue-Bug Needs-Triage
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#20110
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?