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

You have to double hit the key to get the chinese punctuation corretly in vim/neovim in this terminal! #4500

Closed
zyy1998 opened this issue Feb 7, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@zyy1998
Copy link

zyy1998 commented Feb 7, 2020

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version: v0.8.10261.0 and 2019/6/21 published on MS-Store
NeoVim version: 0.4.3
Input method editor: Microsoft Pinyin

Steps to reproduce

  1. Install vim/neovim
  2. Open powershell in the terminal and type nvim test.md
  3. Switch to Chinese input method editor
  4. Feel free to type some Chinese punctuation like ,。?!() and you'll get what I say

Expected behavior

If I just write in English in the terminal, it performs pretty well. And I have tested it in cmder and nvim-qt.exe, have no problem.
20200207184039
( BTW, nvim-qt is not a terminal actually )

20200207185123

Actual behavior

In windows terminal, whatever I use nvim in powershell or vim in WSL bash, I have to hit the key twice in order to input the Chinese punctuation. So I pretty sure it's a bug of windows terminal.

More interested, you need not have to hit the same key twice, just hit whatever first and then hit what you want to input, it seems that the first key has been eaten by terminal.

Most interested is: I clicked some emoji in MS pinyin with the mouse, but it did not appear here immediately., when I typed some Chinese ( NOT ENGLISH ), all the emojis swarm into my terminal.

20200207193010

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 7, 2020
@DHowett-MSFT
Copy link
Contributor

Thanks for the report! This sounds like a /dupe of #3745

@ghost
Copy link

ghost commented Feb 7, 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 Feb 7, 2020
@ghost ghost 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 Needs-Tag-Fix Doesn't match tag requirements labels Feb 7, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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