Preview_1.20.10303.0_x64, vim and nano, Keyboard Numeric keypad, not working. #21190

Closed
opened 2026-01-31 07:35:52 +00:00 by claunia · 4 comments
Owner

Originally created by @k9fvm on GitHub (Feb 3, 2024).

Windows Terminal version

WindowsTerminalPreview_1.20.10303.0_x64.zip

Windows build number

10.0.22631.0

Other Software

vim 9.1
nano 7.2

Steps to reproduce

WindowsTerminalPreview_1.20.10303.0_x64.zip
Extract the file.
Create the file .portable in the folder.
Using ssh --> Linux, or Using msys2.
Open vim or nano.

Expected Behavior

No response

Actual Behavior

vim:
Keyboard Numeric keypad , 'Numpad_3' and 'Numpad_9' , not working.
nano:
Keyboard Numeric keypad , ALL Numpad , not working.

Originally created by @k9fvm on GitHub (Feb 3, 2024). ### Windows Terminal version WindowsTerminalPreview_1.20.10303.0_x64.zip ### Windows build number 10.0.22631.0 ### Other Software vim 9.1 nano 7.2 ### Steps to reproduce WindowsTerminalPreview_1.20.10303.0_x64.zip Extract the file. Create the file .portable in the folder. Using ssh --> Linux, or Using msys2. Open vim or nano. ### Expected Behavior _No response_ ### Actual Behavior vim: Keyboard Numeric keypad , 'Numpad_3' and 'Numpad_9' , not working. nano: Keyboard Numeric keypad , ALL Numpad , not working.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:35:52 +00:00
Author
Owner

@dziban303 commented on GitHub (Feb 4, 2024):

This is happening to me too. I'm also on 1.20.10303.0_x64. In any linux session I start, the numeric keypad keys try to do functions instead of write numerals when in nano, but functions normally at the command line. Powershell or cmd sessions work normally.

@dziban303 commented on GitHub (Feb 4, 2024): This is happening to me too. I'm also on 1.20.10303.0_x64. In any linux session I start, the numeric keypad keys try to do functions instead of write numerals when in `nano`, but functions normally at the command line. Powershell or cmd sessions work normally.
Author
Owner

@j4james commented on GitHub (Feb 4, 2024):

See issue https://github.com/microsoft/terminal/issues/16654#issuecomment-1925438704.

@j4james commented on GitHub (Feb 4, 2024): See issue https://github.com/microsoft/terminal/issues/16654#issuecomment-1925438704.
Author
Owner

@DHowett commented on GitHub (Feb 5, 2024):

Yep, this is a /duplicate of #16654! Thanks!

@DHowett commented on GitHub (Feb 5, 2024): Yep, this is a /duplicate of #16654! Thanks!
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Feb 5, 2024):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 5, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21190