Chinese IME malfunctioning in integrated terminal search box
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.59.0-insider
- OS Version: Windows 10 10.0.19043.1110
Steps to Reproduce:
- have a Chinese IME installed, I use Microsoft IME
- (press ctrl+`) open integreted terminal
- (press ctrl+f) open search dialog
- (press win+space maybe multiple times) switch input language to Chinese (you might need to install one)
- switch the Microsoft Input IME to Chinese mode, type in some words, for example (nihao / 你好)
- the behavior looks like the follwing GIF
and it shoud work like this (demonstrate in notepad.exe)
this bug appears in both release version and insider version
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Visual Studio Integrated Terminal cannot display some ...
When typing certain Chinese characters into the integrated terminal, the Unicode placeholder appears instead. However, if the characters are ...
Read more >Chinese IME dictionaries are not ready yet - Windows
The issue occurs because the Chinese IME dictionaries are included in the basic typing package of Features on Demand (FODs) instead of Windows ......
Read more >Documentation - iTerm2 - macOS Terminal Replacement
When you open the find field (cmd-f) there is a down-arrow on the left of the ... The integration allows you to see...
Read more >Writing Chinese - EmacsWiki
It is a self contained input method in pure elisp. I tried the pinyin engine, it works fine in emacs GUI and terminal...
Read more >Character Input Method and Apparatus, and Terminal - Justia Patents
A character input method and apparatus, and a terminal, where in the method, a candidate character box is a sliding display box capable...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I manually bisected earlier versions, it seems a regression v1.51 is good https://code.visualstudio.com/updates/v1_51 v1.56 is good https://code.visualstudio.com/updates/v1_56 v1.57 is good https://code.visualstudio.com/updates/v1_57 v1.58 is broken https://code.visualstudio.com/updates/v1_58 v1.59 is broken https://code.visualstudio.com/updates/v1_59
Reopen this issue since it occured again in 1.70.1 (user setup)