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

Ctrl+H not detected properly #6321

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

Originally created by @vincentfiestada on GitHub (Feb 6, 2020).

Environment

Windows build number: Microsoft Windows NT 10.0.18363.0
Windows Terminal version: 0.8.10261.0

Other software:
NVIM v0.4.3

See here for the contents of profile.json and init.vim.

Steps to reproduce

  1. Open Neovim.
    • I have mapped CtrlH to switch to the left window
    • I have verified that CtrlH is not a keybinding in Windows Terminal's profile.json
  2. Open the NERDTree file browser; or, open two windows in vertical split.
  3. With the cursor in the rightmost window, in Normal mode, press CtrlH to switch to the leftmost window.

Expected behavior

The cursor should move to the leftmost window.
Note that doing the same steps in pwsh.exe and cmd.exe in the old command-line, Neovim behaves as expected.

Neovim on pwsh.exe in the old command-line ✔️
Neovim on pwsh.exe in the old command-line

Neovim on cmd.exe in the old command-line ✔️
Neovim on cmd.exe in the old command-line

Actual behavior

The cursor only moves left one character. This should happen if I press only the H key.

Neovim on pwsh.exe in Windows Terminal

The issue persists on cmd.exe in Windows Terminal.

Originally created by @vincentfiestada on GitHub (Feb 6, 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 NT 10.0.18363.0 Windows Terminal version: 0.8.10261.0 Other software: NVIM v0.4.3 ``` See [here](https://gist.github.com/vincentfiestada/0f7de76bde603373447ec3e5c20fca30) for the contents of `profile.json` and `init.vim`. # Steps to reproduce 1. Open Neovim. - I have mapped <kbd>Ctrl</kbd><kbd>H</kbd> to switch to the left window - I have verified that <kbd>Ctrl</kbd><kbd>H</kbd> is not a keybinding in Windows Terminal's `profile.json` 2. Open the NERDTree file browser; or, open two windows in vertical split. 3. With the cursor in the rightmost window, in Normal mode, press <kbd>Ctrl</kbd><kbd>H</kbd> to switch to the leftmost window. # Expected behavior The cursor should move to the leftmost window. Note that doing the same steps in `pwsh.exe` and `cmd.exe` in the old command-line, Neovim behaves as expected. Neovim on `pwsh.exe` in the old command-line ✔️ ![Neovim on `pwsh.exe` in the old command-line](https://media.giphy.com/media/Tf4NUDY5pS9fbfibcP/giphy.gif) Neovim on `cmd.exe` in the old command-line ✔️ ![Neovim on `cmd.exe` in the old command-line](https://media.giphy.com/media/KfCHPGmN2Vh7eLgia0/giphy.gif) # Actual behavior The cursor only moves left one character. This should happen if I press _only_ the <kbd>H</kbd> key. ![Neovim on `pwsh.exe` in Windows Terminal](https://media.giphy.com/media/W5fOWlFlaBhHPaNAXE/giphy.gif) The issue persists on `cmd.exe` in Windows Terminal.
claunia added the Resolution-Duplicate label 2026-01-31 00:35:43 +00:00
claunia commented 2026-01-31 00:35:44 +00:00
Author
Owner
Copy Link

@vincentfiestada commented on GitHub (Feb 6, 2020):

I should also note that this issue did not exist before, so I suspect the new version of Windows Terminal introduced this bug.

@vincentfiestada commented on GitHub (Feb 6, 2020): I should also note that this issue did not exist before, so I suspect the new version of Windows Terminal introduced this bug.
claunia commented 2026-01-31 00:35:44 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 6, 2020):

This sounds like the same issue as #4397.

@j4james commented on GitHub (Feb 6, 2020): This sounds like the same issue as #4397.
claunia commented 2026-01-31 00:35:45 +00:00
Author
Owner
Copy Link

@vincentfiestada commented on GitHub (Feb 7, 2020):

I'm not that familiar with the intricacies of how input sequences interpreted, but after reading #4397 and #3935 it seems this was a trade-off due to the requirement of supporting both native and WSL programs??

But I guess until #879 is fixed, I'll have to rebind those commands to other keys.

@vincentfiestada commented on GitHub (Feb 7, 2020): I'm not that familiar with the intricacies of how input sequences interpreted, but after reading #4397 and #3935 it seems this was a trade-off due to the requirement of supporting both native and WSL programs?? But I guess until #879 is fixed, I'll have to rebind those commands to other keys.
claunia commented 2026-01-31 00:35:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 7, 2020):

Thanks for finding the dupe. Sorry for the inconvenience.

@DHowett-MSFT commented on GitHub (Feb 7, 2020): Thanks for finding the dupe. Sorry for the inconvenience.
claunia commented 2026-01-31 00:35:45 +00:00
Author
Owner
Copy Link

@cristiandonosoc commented on GitHub (Jun 10, 2021):

The issue this was pointed to says it was fixed, but I'm still seeing this issue on Windows Terminal Preview 1.9.1523.0, so I'm guessing not all sequences are covered?

I have this literal same issue. Show I open a new issue or re-opening this one is the correct way to go?
Thank you

@cristiandonosoc commented on GitHub (Jun 10, 2021): The issue this was pointed to says it was fixed, but I'm still seeing this issue on Windows Terminal Preview 1.9.1523.0, so I'm guessing not all sequences are covered? I have this literal same issue. Show I open a new issue or re-opening this one is the correct way to go? Thank you
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 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#6321
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?