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

Windows terminal unbound keys are not being recorded by applications #5458

New Issue
Closed
opened 2026-01-31 00:13:52 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:13:52 +00:00
Owner
Copy Link

Originally created by @maximebl on GitHub (Dec 8, 2019).

Originally assigned to: @DHowett-MSFT on GitHub.

Environment

Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Any other software?

Windows Terminal version 0.7.3291.0
Vim version 8.1.2102 (Windows vim, not WSL)

Steps to reproduce

Unbind a key chord the following way:

    "keybindings" : 
    [        
        {
            "command" : "none",
            "keys" : 
            [
                "ctrl+shift+up"
            ]
        }
    ]

Expected behavior

The key chord should now be useable by applications running inside the Windows terminal. For example Vim or Emacs.

Actual behavior

The applications do not receive the key chord at all.

Originally created by @maximebl on GitHub (Dec 8, 2019). Originally assigned to: @DHowett-MSFT on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 ```none Any other software? ``` Windows Terminal version `0.7.3291.0` Vim version `8.1.2102` (Windows vim, not WSL) # Steps to reproduce Unbind a key chord the following way: ``` "keybindings" : [ { "command" : "none", "keys" : [ "ctrl+shift+up" ] } ] ``` # Expected behavior The key chord should now be useable by applications running inside the Windows terminal. For example Vim or Emacs. # Actual behavior The applications do not receive the key chord at all.
claunia added the Issue-BugArea-InputResolution-DuplicateProduct-Terminal labels 2026-01-31 00:13:53 +00:00
claunia commented 2026-01-31 00:13:54 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 8, 2019):

Can't reproduce this:

image

^[[1;6A is the encoding for Ctrl+Shift+Up.

@DHowett-MSFT commented on GitHub (Dec 8, 2019): Can't reproduce this: ![image](https://user-images.githubusercontent.com/14316954/70382390-33f3ac80-1910-11ea-8e32-a0d707bd6a00.png) `^[[1;6A` is the encoding for <kbd>Ctrl+Shift+Up</kbd>.
claunia commented 2026-01-31 00:13:54 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 8, 2019):

(also: you said "no other software", but.. you didn't include your Terminal version, emacs verison, vim version, WSL distribution, whether you're using Windows vim/emacs or WSL vim/emacs, etc. Please fill out the template: it helps us help you, and we will close bugs that do not have enough information in them.)

@DHowett-MSFT commented on GitHub (Dec 8, 2019): (also: you said "no other software", but.. you didn't include your Terminal version, emacs verison, vim version, WSL distribution, whether you're using Windows vim/emacs or WSL vim/emacs, etc. Please fill out the template: it helps us help you, and we _will_ close bugs that do not have enough information in them.)
claunia commented 2026-01-31 00:13:54 +00:00
Author
Owner
Copy Link

@maximebl commented on GitHub (Dec 8, 2019):

I updated my original report with the missing information. Sorry about that! I didn't include it in my last report without a fuss so I figured it wasn't necessary but it's pretty clear it matters a lot!

In vim you can type : and then do ctrl+k and then a key chord and it will tell you what key you pressed. When I try that in the Windows terminal under windows I get nothing at all back, vim doesn't even know I pressed a key at all it seems.

When I try the same thing while running vim under WSL, the command correctly reports back that I pressed ctrl+shift+up.

@maximebl commented on GitHub (Dec 8, 2019): I updated my original report with the missing information. Sorry about that! I didn't include it in my last report without a fuss so I figured it wasn't necessary but it's pretty clear it matters a lot! In vim you can type `:` and then do `ctrl+k` and then a key chord and it will tell you what key you pressed. When I try that in the Windows terminal under windows I get nothing at all back, vim doesn't even know I pressed a key at all it seems. When I try the same thing while running vim under WSL, the command correctly reports back that I pressed ctrl+shift+up.
claunia commented 2026-01-31 00:13:54 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 8, 2019):

Thanks for filling out the template! This is interesting. It might be #2397, but if it’s not it’s a similar codepath. Windows Vim receives keyboard events in a different way than WSL Vim.

@DHowett-MSFT commented on GitHub (Dec 8, 2019): Thanks for filling out the template! This is interesting. It might be #2397, but if it’s not it’s a similar codepath. Windows Vim receives keyboard events in a different way than WSL Vim.
claunia commented 2026-01-31 00:13:54 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 23, 2020):

Until we learn otherwise, this is a /dup of #2397. Thanks!

@DHowett-MSFT commented on GitHub (Jan 23, 2020): Until we learn otherwise, this is a /dup of #2397. Thanks!
claunia commented 2026-01-31 00:13:55 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 23, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jan 23, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Area-Input Issue-Bug Product-Terminal Resolution-Duplicate
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#5458
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?