ctrl+shift+f shortcut not work in vscode 1.26.1

[braveheart4217]

• VSCode Version: 1.26.1
• OS Version: Windows 10

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

if i cahnge findInFiles( default: ctrl+shift+f ) to another shortcut, it works

[alexdima]

What does VS Code detect when you press the desired key combination? Please hover over the input box and take a screenshot:

[braveheart4217]

when i press ctrl + shift + f, vscode shows this

[braveheart4217]

but when i selected in explorer, ctrl + shift + f works

[alexdima]

That is bizzare. The received key code is 229 (0xE5) which is VK_PROCESSKEY according to this table

I would have expected that you would receive the key code for F, 70 (0x46). Does ctrl+shift+F hold some special meaning under your input mode? What keyboard layout / input mode are you using? Does this reproduce when changing the keyboard layout to English ?

[braveheart4217]

when i change the keyboard layout to English, it works.
it seems it's the windows chinese input mode calls this problem.

but before i update, everythings is ok, is there something makes it?

finally，thanks you help me fix this annoying problem。

[alexdima]

@braveheart4217 So this key combination was being interpreted correctly in VSCode 1.25? Here is a download link for a 1.25.1 zip - https://az764295.vo.msecnd.net/stable/1dfc5e557209371715f655691b1235b6b26a06be/VSCode-win32-x64-1.25.1.zip

[pohmelie]

I have similar issue, but on ubuntu 18.04. After update to 1.26 my ctrl+shift+E stops working, keybinding helper shows ctrl+shift+unknown on ctrl+shift+E pressed. But system key bindings in KDE shows right combination.

[alexdima]

@pohmelie IMHO your issue cannot be possibly be related to this issue, as this issue is about Windows, and your issue is about Ubuntu. Those two operating systems have completely different keyboard input handling methods that result in different code paths for both VS Code and Chromium. I'm not sure what your problem could be, but you can open a new issue if you need help.

But bear in mind, we haven't had to do a code change in the keyboard handling code of VS Code since about 1 year. i.e. things always end up being covered by https://github.com/Microsoft/vscode/wiki/Keybinding-Issues or being some weird environmental problem.

[pohmelie]

@alexandrudima
I agree, that this is probably ubuntu issue, since recently I have updates with "keyboard" word in package name (don't remember package full name). I will test this at home on ubuntu 17.10, it support dropped, so there is already "stable" state for month or greater. Thanks!

[braveheart4217]

@alexandrudima i have tryed the vscode you just give me, it's the same issue with the 1.26.1，and i have find ctrl+shift+f used in sougou Input（an input app）, i closed shortcut in that app, then it works in sougou input, but it still can't work in windows chinese input mode

[alexdima]

i have tried the vscode you just give me, it's the same issue with the 1.26.1

This indicates to me that this was not a recent regression from our side.

Are you able in any other software on this machine to get Ctrl+Shift+F to do anything meaningful when you are using the Windows Chinese Input Mode ?

[braveheart4217]

oh shit, ctrl+shift+f is the shortcut to switch Simplified or Traditional in Windows Chinese Input Mode

[alexdima]

👍 That solves the mystery! :)