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

Alt+Numpad not working #657

Closed
tkmikan opened this issue May 10, 2019 · 6 comments
Closed

Alt+Numpad not working #657

tkmikan opened this issue May 10, 2019 · 6 comments
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Help Wanted We encourage anyone to jump in on these. Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Milestone

Comments

@tkmikan
Copy link

tkmikan commented May 10, 2019

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    10.0.18362.86
  • What you're doing and what's happening:
    Using ALT+numpad to input some characters by their code. For example I'm typing ALT+97 to enter a
    • in cmd in terminal: 9 and 7 appear when hitted, and a appears when releasing ALT
    • in powershell in terminal: digit-argument is triggered, so a is duplicated 97 times when releasing ALT
  • What's wrong / what should be happening instead:
    should have same behavior as outside the terminal

Perhap it is similar to #637

@zadjii-msft
Copy link
Member

Adding support for this is in PR currently, #623.

@zadjii-msft zadjii-msft added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label May 10, 2019
@tkmikan
Copy link
Author

tkmikan commented May 12, 2019

Actually I mean all inputs should be blocked when holding ALT, except for those shortcuts. This issue does not have much to do with #623

@zadjii-msft
Copy link
Member

Ah okay, I see what you mean now. Yea, #623 probably even makes this worse. I'll change this to a bug.

@zadjii-msft zadjii-msft added Area-Input Related to input processing (key presses, mouse, etc.) Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Area-UserInterface Issues pertaining to the user interface of the Console or Terminal Help Wanted We encourage anyone to jump in on these. Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Area-UserInterface Issues pertaining to the user interface of the Console or Terminal labels May 12, 2019
@zadjii-msft zadjii-msft added this to the Windows Terminal v1.0 milestone May 12, 2019
@zadjii-msft zadjii-msft reopened this May 12, 2019
@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label May 17, 2019
@miniksa miniksa added Product-Terminal The new Windows Terminal. and removed Mass-Chaos labels May 17, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label May 17, 2019
@encladeus
Copy link

The behavior of this bug seems to have slightly changed with 0.3, but is still not working correctly in cmd, powershell or ubuntu. Here are a couple of screen shots from Ubuntu running on WSL.

While holding down the Alt key and entering 148 (Alt + 148):
ubuntu-alt

Then when the Alt key is released, it clears the argument line above and replaces the command line with 148 ö chars.
ubuntu-release

Similarly, if I enter Alt + 141 there are 141 ì chars output on the command line.

@miniksa
Copy link
Member

miniksa commented Jan 28, 2020

/dup #1401

I know this is the older one, but that one has a bit more code info in it and seems to be similar enough.

@ghost
Copy link

ghost commented Jan 28, 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 ghost closed this as completed Jan 28, 2020
@ghost ghost added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jan 28, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Help Wanted We encourage anyone to jump in on these. Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Terminal The new Windows Terminal. 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