-
Notifications
You must be signed in to change notification settings - Fork 34.5k
Closed
Labels
author-verification-requestedIssues potentially verifiable by issue authorIssues potentially verifiable by issue authorbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bughelp wantedIssues identified as good community contribution opportunitiesIssues identified as good community contribution opportunitiesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersterminalGeneral terminal issues that don't fall under another labelGeneral terminal issues that don't fall under another labelupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)upstream-issue-fixedThe underlying upstream issue has been fixedThe underlying upstream issue has been fixedupstream-issue-linkedThis is an upstream issue that has been reported upstreamThis is an upstream issue that has been reported upstreamverifiedVerification succeededVerification succeeded
Milestone
Description
- VSCode Version: 1.39.1
- OS Version: Microsoft Windows (Pro) Version 1903 (OS Build 10.18362.418)
- PowerShell Version: 5.1
Steps to Reproduce:
- Open VSCode
- Open a Terminal
- Make keyboard keys input combination of "AltGr + 2 then Space" or "AltGr + 7 then Space"
- You get the standard key (unexpected) plus the AltGr key (expected)
This happens on an AZERTY keyboard (a Surface Type Cover). I am not able to confirm if this happens on QWERTY too.
On AZERTY keyboards, the keys "2" and "7" consist in 3 characters:
- Keyboard key "2": é (standard) + 2 (shift) + ~ (AltGr+Space)
- Keyboard key "7": è (standard) + 7 (shift) + ` (AltGr+Space)
Note: This dysfunction only affects PowerShell through VSCode. Code workspace is not affected. And native PowerShell also behaves perfectly.
These keys are quite intensively used. Any solution would be appreciated.
Does this issue occur when all extensions are disabled?: Yes
jlmeunier, amongonz, dleborgne, elboletaire, u1735067 and 1 more
Metadata
Metadata
Assignees
Labels
author-verification-requestedIssues potentially verifiable by issue authorIssues potentially verifiable by issue authorbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bughelp wantedIssues identified as good community contribution opportunitiesIssues identified as good community contribution opportunitiesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersterminalGeneral terminal issues that don't fall under another labelGeneral terminal issues that don't fall under another labelupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)upstream-issue-fixedThe underlying upstream issue has been fixedThe underlying upstream issue has been fixedupstream-issue-linkedThis is an upstream issue that has been reported upstreamThis is an upstream issue that has been reported upstreamverifiedVerification succeededVerification succeeded