Some Ctrl+Alt+ shortcuts no longer work when AltGr+ is pressed #68787
Comments
|
@Gooseman This happens on the right Alt key? Or on both? |
|
On both.
…On Fri, Feb 15, 2019 at 6:55 PM Kai Maetzel ***@***.***> wrote:
@Gooseman <https://github.com/Gooseman> This happens on the right Alt
key? Or on both?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68787 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD0GOJgo8TlQAzpJYxQ1aGaOvEPljXT2ks5vNwK3gaJpZM4a9zsl>
.
|
|
I have the same problem with the PlatformIO extension. It uses CTRL+ALT+u to upload code to an Arduino. On my old laptop this works (outside of the App I get ú when I press those keys, but in the app, the shortcut takes precedence. On a fresh install of Windows 10 Pro, with a fresh install of VS Code, and the PlatformIO extension I get ú when I press the shortcut keys. On the OS that works, I have v10.0.17134, and the one that doesn't work has v10.0.17763. All other apsects of VS Code are exactly the same as in the original post |
|
I also have the same problem: the right CTRL+ALT keys doesn't work for a shortcut. It works if I press the left CTRL+ALT keys. |
|
Leandro - not quite the same problem. I get the same behaviour regardless
of which Ctrl and Alt keys I use. Also, for combinations that don't result
in accented characters in other applications, I get the configured shortcut
executing in VS Code. It's only some Ctrl+Alt shortcuts that don't work.
…On Sun, Feb 17, 2019 at 2:55 PM Leandro ***@***.***> wrote:
I also have the same problem: the right CTRL+ALT keys doesn't work for a
shortcut. It works if I press the left CTRL+ALT keys.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68787 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD0GOI5qqh1FwA5wVhGCyoLaVHJhdefrks5vOW17gaJpZM4a9zsl>
.
|
|
It seems to be the shortcuts that would have inputted a unicode character that now fail. However, CTRL+ALT+u is a short cut for "upload" with the PlatformIO extension. On a different (older) Windows 10 install with VS Code, the shortcut works, but on a fresh install -completed in the last couple of days - the shortcut doesn't work, and the unicode character overrides it. |
|
With the latest release, 1.32.0, Ctrl+alt+<vowel> works, but
Ctrl+alt+shift+<vowel> (which was working) is now broken...
…On Tue, Feb 19, 2019 at 8:20 PM Richard Scott ***@***.***> wrote:
It seems to be the shortcuts that would have inputted a unicode character
that now fail.
Such as:
CTRL+ALT+o = ó
CTRL+ALT+a = á
CTRL+ALT+o = é
CTRL+ALT+u = ú
However, CTRL+ALT+u is a short cut for "upload" with the PlatformIO
extension.
On a different (older) Windows 10 install with VS Code, the shortcut
works, but on a fresh install -completed in the last couple of days - the
shortcut doesn't work, and the unicode character overrides it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68787 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD0GONqIx9w5eVIfQEHm5zwkL-i8RBQQks5vPFx0gaJpZM4a9zsl>
.
|
|
I've had to write a new windows keyboard map to get round this ;-( On here it suggests this procedure to create a new keyboard layout.
Then we need to apply this new keyboard layout.
|
|
Intricate solution @richard-scott, but perhaps a little bit of overkill.. |
|
My problem was related to run MySQL queries inside VSCode, by pressing ctrl + alt + E. My solution was to change the keyboard shortcut from ctrl + alt + E to ctrl + alt + backspace, which is easier to type. =] I followed the instructions on this video (image): https://cloud.githubusercontent.com/assets/5047891/25484174/38f5b004-2b59-11e7-994b-dfa96ef043ce.gif |
|
This issue is still happening as of today (i.e. using shortcuts like What is strange is that I have the same exact layout in a different computer, and this problem does NOT happen there. Is this something that can be fixed/broken by a Windows update? I currently have no clue about what could fix this. VSCode info; |
|
This doesn't seem to be a VS Code issue. Rather, Windows seems to have made it a bit easier to input regional Unicode characters. Any sort of 'extended' or 'international' version of the keyboard will reproduce this issue with specific characters. Just change keyboard layout to 'US' or 'United Kingdom' to at least have access to non-vowel shortcuts. Steps to fix consonants:
At least the consonants should be fixed now. |
|
Nishnat-Rishi - I haven't seen anyone complaining about problems with
consonants, only vowels.
The problem is not related to the keyboard layout. I don't switch my
keyboard layout and sometimes when I use a key combination that includes
Ctrl, Alt and a vowel I don't get the shortcut I've configured, but rather
an accented vowel. Sometimes I get the keyboard shortcut. I can go for
hours or days having no problems and then I'll have hours or days during
which all my keyboard shortcuts that include Ctrl, Alt and a vowel give me
the accented vowel instead. This behaviour is also happening across
keyboards as well as computers. I'm not changing keyboard layouts while
I'm working and my computers use the same UK keyboard layout. The idea of
doing things like changing keyboard layouts was brought up when I first
reported this problem. Changing keyboard layouts and languages didn't work
then and it doesn't work now. There's also the fact that VS Code is the
only application in which this happens. All my shortcuts in Visual Studio
work as expected all the time. All my shortcuts in IntelliJ work as
expected all the time. All my shortcuts in VIM work as expected all the
time.
The consonants work anyway in general since Ctrl + Alt + consonant doesn't
generally give an accented consonant, it'll just run the shortcut if one is
configured.
…On Fri, Jan 31, 2020 at 5:45 AM nishnat-rishi ***@***.***> wrote:
This doesn't seem to be a VS Code issue. Rather, Windows seems to have
made it a bit easier to input regional Unicode characters. Any sort of
'extended' or 'international' version of the keyboard will reproduce this
issue with specific characters. Just change keyboard layout to 'US' or
'United Kingdom' to at least have access to non-vowel shortcuts.
Steps to fix consonants:
- Go to 'Advanced keyboard settings'. Ensure the drop-down menu option
under 'Override for default input method' is set to 'Use language list
(Recommended)'.
- Go to 'Language settings', Make sure under 'Preferred languages',
first option is set to 'English (United States)'. or 'English (United
Kingdom)' Click on it. Click on 'Options'.
- Under 'Keyboards', remove whatever keyboard is there, and add 'US'
or 'United Kingdom' keyboard instead.
At least the consonants should be fixed now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68787?email_source=notifications&email_token=AA6QMOEUBCV7UGOIYU42QLTRAO3I3A5CNFSM4GXXHMS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNR77Y#issuecomment-580591615>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6QMOFGZDVLWCLIFQLLSWLRAO3I3ANCNFSM4GXXHMSQ>
.
|
|
it's 2020 3.7 .it has the same question.
|
|
Other programs, like CLion, are able to discern between |
|
Just to add this problem is biting me too - almost certain it is caused by a windows update / rebuild... I am now on version 1909, (build 18363.836) thx. |
Just change your keyboard to US layout. It works for me. |
|
" Just change your keyboard to US layout. It works for me."
Ah, yes, the old, "Do the wrong thing to sort out a problem that shouldn't
exist." I mean, it's not like anyone should expect software to work, after
all. I'm going to try that with my employer. "Just type in the correct
numbers, that works for me when the calculated value is incorrect."
…On Thu, Jun 4, 2020 at 6:36 AM Ankit Raj ***@***.***> wrote:
This issue is still happening as of today (i.e. using shortcuts like
Ctrl+Alt+Aor Ctrl+Alt+E inserts á and é). I'm using the "United Kingdom
Extended keyboard" layout in Windows.
What is strange is that I have the same exact layout in a different
computer, and this problem does NOT happen there. Is this something that
can be fixed/broken by a Windows update? I currently have no clue about
what could fix this.
VSCode info;
Version: 1.41.1 (user setup)
Commit: 26076a4
Date: 2019-12-18T14:58:56.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362
Just change your keyboard to US layout. It works for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68787 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6QMOGBIUXENCJ5JCN32EDRU4XGZANCNFSM4GXXHMSQ>
.
|
well that's a work around, thanks for mentioning it. |
I can confirm this problem with consonants. For example, on a US International keyboard |
|
I see this is still open. Any ETA on a fix? I use InteliJ's shortcuts and ctrl + alt + L to format a file ends up inserting an ø... |
|
I amhaving the issue aswell. I tried what @nishnat-rishi said here but it didn't worked out. |
This is the same for me, I have also tried this. I am unable to bind CTRL + ALT + UP and the same with CTRL + ALT + DOWN. Would be nice to see a solution to this! Although I'm not entirely sure if my issue is related, might not be 🤔. I can bind UP + DOWN separately, but not when using CTRL + ALT |
I'm having the exact same issue as @KebbleyTea. I can bind UP and DOWN separately, but I can't bind then when using CTRL+ALT. |
|
I noticed the issue also happened in visual studio. I think it's not related to vs code. It somehow got fixed after the latest windows update. |
Facing the same problem, but LEFT and RIGHT are also affected |
|
Had this exact issue today all of a sudden, everything worked fine yesterday. I assigned the key combination Still an issue that it worked fine yesterday on the CTRL + ALT + SHIFT + N [2022-04-06 13:46:20.566] [renderer1] [info] [KeybindingService]: / Received keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control
[2022-04-06 13:46:20.567] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl')
[2022-04-06 13:46:20.567] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2022-04-06 13:46:20.751] [renderer1] [info] [KeybindingService]: / Received keydown event - modifiers: [ctrl,shift], code: ShiftLeft, keyCode: 16, key: Shift
[2022-04-06 13:46:20.751] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl,shift], code: ShiftLeft, keyCode: 4 ('Shift')
[2022-04-06 13:46:20.751] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2022-04-06 13:46:20.879] [renderer1] [info] [KeybindingService]: / Received keydown event - modifiers: [ctrl,shift,alt], code: AltLeft, keyCode: 18, key: Alt
[2022-04-06 13:46:20.879] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl,shift,alt], code: AltLeft, keyCode: 6 ('Alt')
[2022-04-06 13:46:20.879] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2022-04-06 13:46:21.343] [renderer1] [info] [KeybindingService]: / Received keydown event - modifiers: [shift], code: KeyN, keyCode: 78, key: Ñ
[2022-04-06 13:46:21.343] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [shift], code: KeyN, keyCode: 44 ('N')
[2022-04-06 13:46:21.343] [renderer1] [info] [KeybindingService]: | Resolving shift+N
[2022-04-06 13:46:21.343] [renderer1] [info] [KeybindingService]: \ No keybinding entries.
[2022-04-06 13:46:21.614] [renderer1] [info] [KeybindingService]: + Ignoring single modifier ctrl due to it being pressed together with other keys.CTRL + ALT + C CTRL + ALT + J [2022-04-06 13:47:06.782] [renderer1] [info] [KeybindingService]: / Received keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control
[2022-04-06 13:47:06.783] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl')
[2022-04-06 13:47:06.783] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2022-04-06 13:47:06.886] [renderer1] [info] [KeybindingService]: / Received keydown event - modifiers: [ctrl,alt], code: AltLeft, keyCode: 18, key: Alt
[2022-04-06 13:47:06.887] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl,alt], code: AltLeft, keyCode: 6 ('Alt')
[2022-04-06 13:47:06.887] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
[2022-04-06 13:47:07.086] [renderer1] [info] [KeybindingService]: / Received keydown event - modifiers: [], code: KeyC, keyCode: 67, key: ©
[2022-04-06 13:47:07.087] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: KeyC, keyCode: 33 ('C')
[2022-04-06 13:47:07.087] [renderer1] [info] [KeybindingService]: | Resolving C
[2022-04-06 13:47:07.087] [renderer1] [info] [KeybindingService]: \ From 1 keybinding entries, no when clauses matched the context.
[2022-04-06 13:47:07.806] [renderer1] [info] [KeybindingService]: / Received keydown event - modifiers: [ctrl,alt], code: KeyJ, keyCode: 74, key: j
[2022-04-06 13:47:07.807] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl,alt], code: KeyJ, keyCode: 40 ('J')
[2022-04-06 13:47:07.807] [renderer1] [info] [KeybindingService]: | Resolving ctrl+alt+J
[2022-04-06 13:47:07.807] [renderer1] [info] [KeybindingService]: \ No keybinding entries.
[2022-04-06 13:47:08.030] [renderer1] [info] [KeybindingService]: + Ignoring single modifier ctrl due to it being pressed together with other keys. |
When the On-Screen keyboard is open, go to Options | Turn on numeric key pad | Num Lock. That's all... |
|
I gave up on this. I don't know what the heck is going on. I just replaced "Add Cursor Above/Below" with "Ctrl+Shift+UpArrow/DownArrow"...so annoying. |
Thanks a lot!!! It Worked for me!!!! |
|
It is caused by the keyboard layout language. I fixed it for myself by making sure I use 'US English' layout when working in VSCode. |
alexdima
changed the title
|
Trying to summarise what I know on this topic:
|
alexdima
changed the title
alexdima
added
feature-request
vscodenpa
added
unreleased
bhavyaus
added
verification-steps-needed
rzhao271
added
verified
|
I verified that the keyboard shortcuts in #68787 (comment) work again for the US-International layout after |
and others
I have several shortcuts defined using Ctrl+Alt+. The ones that have a vowel no longer execute the shortcut, but instead insert an accented character. This started with the latest update -
Version: 1.31.1 (user setup)
Commit: 1b8e830
Date: 2019-02-12T02:20:54.427Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 6.1.7601
The keyboard shortcuts that no longer work
{
"key": "ctrl+alt+e",
"command": "cursorLineEnd",
"when": "editorTextFocus"
},
{
"key": "ctrl+alt+a",
"command": "cursorLineStart",
"when": "editorTextFocus"
},
I've tried this with extensions disabled and in insiders and the result is the same. When I try to add the shortcut using the "Define Keybinding" button, when I type the 'e', the Ctrl and Alt disappear from the editor and only the 'e' is left. The language set in the OS has not changed, nor has the keyboard setup - standard UK keyboard.
How do I restore the shortcuts and remove the accented characters?
Thanks
Craig
The text was updated successfully, but these errors were encountered: