Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
k9fvm opened this issue Feb 3, 2024 · 4 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@k9fvm
Copy link

k9fvm commented 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.

@k9fvm k9fvm added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Feb 3, 2024
@dziban303
Copy link

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.

@j4james
Copy link
Collaborator

j4james commented Feb 4, 2024

See issue #16654 (comment).

@DHowett
Copy link
Member

DHowett commented Feb 5, 2024

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

Copy link
Contributor

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 microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants