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

united states-international keyboard does NOT accept characters which need two keystrokes, e.g. " ' ". #16759

Closed
ejprinz opened this issue Feb 24, 2024 · 5 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

@ejprinz
Copy link

ejprinz commented Feb 24, 2024

Windows Terminal version

1.20.10303.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

  • Install "united states-international" input method.
  • Open Windows Terminal Preview
  • Start Ubuntu 22.04 in Windows Subsystem for Linux
  • Type Single Quote followed by Space

Expected result (like in PowerShell):

  • See Single Quote and Space (this happens in Powershell and also in Windows Terminal - not "Preview")

Observed result:

  • See two Space, don't see Single Quote

This is also observed for Double Quote

Expected Behavior

See Single Quote and Space (this happens in Powershell and also in Windows Terminal - not "Preview")

Actual Behavior

See two Space, don't see Single Quote

@ejprinz ejprinz 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 24, 2024
@DanSM-5
Copy link

DanSM-5 commented Feb 25, 2024

I'm having the same issue with Windows Terminal preview v1.20.10303.0.

It works fine under Stable Windows Terminal v1.18.10301.0

This can be triggered under powershell using a command line text editor like neovim (winget install neovim or scoop install neovim). Other shells like Bash from Git for windows are also affected.

@j4james
Copy link
Collaborator

j4james commented Feb 27, 2024

Thanks for the report, but this is a duplicate #16641 and #16642. It should already be fixed in the nightly Canary build, and I believe the fix is going to be backported to v1.20 soon.

@DHowett
Copy link
Member

DHowett commented Feb 27, 2024

Yep! This is rolling out via the store now. The GitHub release will be up tomorrow morning.

@carlos-zamora
Copy link
Member

Thanks for filing. Marking this as a /dup of #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 28, 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

5 participants