-
Notifications
You must be signed in to change notification settings - Fork 297
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
bug: Can not type @ to include files in chat #2383
Labels
Comments
For context: OS is Win 10 Version 10.0.19045 |
hello i'm having the same problem, ENG FR keyboard layouyt the usual alt + @ won't open the menu in vscode, but using ALT + 6 + 4 worked |
abeatrix
added a commit
that referenced
this issue
Jan 4, 2024
Close #2383 The previous check for Ctrl or AltGraph being pressed was too broad and prevented some default browser shortcuts from working properly, and created blockers for users on different keyboard layouts This fixes it by checking specifically for Ctrl keys combo only. Alt + C is still prevented. ## Test plan <!-- Required. See https://sourcegraph.com/docs/dev/background-information/testing_principles. --> 1. Try using alt + key combos when focusing in input box - this should now work 2. Try pressing alt + c when focusing in input box - this should open the command menu
Thanks @abeatrix , just tried it and works! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v1.0.0
v1.1.1702572663
Describe the bug
When in the chat interface, I can not type
@
to include files for context. Even though I type an@
no@
appears in the chat editor - and subsequently no files can be included.I am working on a german keyboard (QWERTZ) so the keyboard combination should be [ALT GR] + [Q].
Current workaround is using the alt-code: [ALT] + ([NUM-6] + [NUM-4])
Expected behavior
When typing
@
to have an@
appear in the chat window and subsequently get suggestions for files to include as context.Additional context
There seems to be a similar issue with other foreign keyboards already posted on discord: https://discord.com/channels/969688426372825169/1179099930258833540
The text was updated successfully, but these errors were encountered: