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

Caret (^) key on French (Canada) keyboard does not work in 1.20 #16649

Closed
phil-blain opened this issue Feb 1, 2024 · 3 comments
Closed

Caret (^) key on French (Canada) keyboard does not work in 1.20 #16649

phil-blain opened this issue Feb 1, 2024 · 3 comments
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

@phil-blain
Copy link

Windows Terminal version

1.20.10293.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

  • Switch keyboard layout to "French (Canada) - Canadian Multilingual Standard"
  • Open Terminal Preview (1.20)
  • Type the key to the right of the P, which is ^ on physical "French (Canada) Canadian Multilingual Standard" - keyboards, or [ on US keyboards
  • Type Space

Expected Behavior

A caret (^) character appears on the command line.

Actual Behavior

A space appears instead.

Notes:

  • It also happens with the older "French (Canada) - Canadian French Keyboard"
  • It also happens with my custom layout based on "French (Canada) - Canadian Multilingual Standard"
  • I did not find other keys that do not work correctly since I upgraded a couple days ago.

P.S. So glad to finally be able to double click long paths that wrap and have the whole thing selected !!

@phil-blain phil-blain 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 1, 2024
@lhecker
Copy link
Member

lhecker commented Feb 1, 2024

Thanks for the report! I'll be closing this in favor of #16641 which describes the same underlying cause. /dup #16641

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 1, 2024
@phil-blain
Copy link
Author

Thanks! I did read that issue but I was not sure it was related as in my case AltGr is not involved.

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

2 participants