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

Incorrect behavior of AltGr+é/è in Terminal on AZERTY layout #125068

Closed
u1735067 opened this issue Jun 1, 2021 · 1 comment
Closed

Incorrect behavior of AltGr+é/è in Terminal on AZERTY layout #125068

u1735067 opened this issue Jun 1, 2021 · 1 comment
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@u1735067
Copy link

u1735067 commented Jun 1, 2021

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.56.2
  • OS Version: Win 10 19042

Steps to Reproduce:

  1. Enable NumLock (not able to reproduce without)
  2. In the Terminal, type AltGr + é followed by space to obtain ~
  3. Get é~ instead

I found that this is a dup of (all closed) #88156, #73876, #68262, #59438 (2018) and related to uptream xtermjs/xterm.js#2151 / xtermjs/xterm.js#2479, but as this bug is still affecting VSCode (no workaround included in VSCode to make it usable), shouldn't an issue be kept opened here? Maybe a known issues entry?

Please note that using an enhanced layout like https://s.twb.fr/mirror-kbdfrac/kbdfrac.htm (kbdfrac2.exe), with ´ on the & key, produces the same behavior ().

As workaround, we can:

Hope you'll have time to fix this :) (and sorry if I only wasted your time)

@Tyriar
Copy link
Member

Tyriar commented Jun 2, 2021

We maintain the xterm.js repo so we track it over there to try keep the total issue count I need to manage down.

@Tyriar Tyriar closed this as completed Jun 2, 2021
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 2, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jul 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants