-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Ctrl Shift O not working #45646
Comments
It depends on the language mode of the editor that is currently open. Not all language support What's the language mode of the editor you have open? |
Javascript |
Also, please provide repo steps and some example code |
Actually I think I've just found something interesting. Using http://en.key-test.ru/, when I do Running Windows 10.0.14393 Edit: I don't get this issue at home with my mechanical keyboard, only at work with this cheap HP keyboard: http://store.hp.com/UKStore/Merch/Product.aspx?id=WZ972AA&opt=ABU&sel=ACC So I imagine it's a hardware limitation with the keyboard, although I could swear I was using |
@alexandrudima Looks like this is keybinding related? Can you please take a look |
I'm having the same issue in Windows 10 10.0.16299 with javascript and typescript files. Update: I tried the webpage Jazcash mentioned (http://en.key-test.ru/) and the keys light up on inputDown on my Ubuntu VM but they don't on Windows. |
PS. "ctrl+shift+l" isn't being detected either. |
@jeanp413 If "ctrl+shift+o" shows "ctrl+shift+" in the keybinding input, it means that the keypress is not reaching VSCode. Most likely, something installed at the level of the OS is capturing this keybinding. Are you able to use this keybinding successfully in other software on the same machine? |
@alexandrudima you were right. |
@Jazcash do you also have an AMD gpu capturing ctrl+shift+o ? |
Yep, seems like that's the issue! |
Ctrl Shift O for the Go To Symbol bind used to work for me in VSCode, but now it does nothing. My friend is having the same issue (with no extensions installed). This appears to be similar to #40470
I'm using default bindings:
Nothing showing in the console either.
The text was updated successfully, but these errors were encountered: