Repository navigation
AltGR SEQUENCES DO NOT WORK -- Can't type any AltGr combinations in Windows Terminal #521
Description
Your Windows build number:
10.0.18362.86
What you're doing and what's happening:
Trying to enter the @ sign on a Swedish keyboard in a PowerShell console using Alt Gr + 2.
See animated gif:
What's wrong / what should be happening instead:
Windows terminal shows digit-argument instead of outputting the @ sign as expected.
It's possible this is a PEBKAC error somehow but the problem doesn't show up in the normal PowerShell console... 😓
Reacted by Johan Lindfors, Jan Kučera, Fabian Mettler, Paulo Morgado, Mattias Karlsson, minoser, Emil Sundin, Leonard Hecker, Gabriel, Daniel Liland and 95 more
Reacted by Hermès BÉLUSCA - MAÏTO, Karl Wester-Ebbinghaus, Magnus Österlund and Shoki
Activity
patriksvensson commentedon May 7, 2019
Update: Same thing happens with all digits when combined with
Alt Gr.zadjii-msft commentedon May 7, 2019
You know, this is probably on me. We're probably not getting vkey correctly for AltGR combos somewhere in TermControl.cpp, when we get the KeyDown event.
watermelonpizza commentedon May 8, 2019
Kinda unrelated, but what software did you use to get a recording with the keys you pressed in the gif Patrik Svensson (@patriksvensson) ?
patriksvensson commentedon May 8, 2019
Alice Miller (@watermelonpizza) I used Carnac to display the key presses and ScreenToGif to capture the window.
watermelonpizza commentedon May 8, 2019
Oh carnac, awesome thanks! I'll add that to my list of goodies :)
DHowett-MSFT commentedon May 9, 2019
I think this is a duplicate of #487.
DHowett-MSFT commentedon May 9, 2019
Whoops, it looks like the left hand doesn't know what the right hand is doing, and I just created a circular duplicate link.
jozsefsallai commentedon May 9, 2019
Can confirm this issue on Windows version 10.0.18362.30 with Hungarian keyboard layout. The behavior is different, depending on what console I'm using:
149 remaining items
sba923 commentedon Aug 7, 2019
AltGr (
~#{[|`\^@]}¤€) works fine here with a French keyboard, Windows 10 version 1903 build 18362.267, Windows Terminal Preview 0.3.2171.0, and the tab-switching shortcuts set toCtrl+Alt+digit.Good job!
DHowett-MSFT commentedon Aug 7, 2019
Thanks for the confirmation!
sba923 commentedon Aug 7, 2019
You're very welcome!
henrik-jensen commentedon Aug 7, 2019
0.3.2171.0 fix confirmed for my system - Danish keyboard Win10 Home 1903 build 10.0.18362.267.
Deleted my
profiles.jsonto get default settings and now AltGr also works for a new install ( I assume ).Great job Leonard Hecker (@lhecker) and everybody else involved.
beppler commentedon Dec 3, 2019
Hi I think I have this problem on version 0.7.
I can not enter the slash key on my keyboard either using the numeric keypad ou AltGr+Q (Brazilian ABTN2 keyboard of an Samsung laptop that doe not have the question mark/slash key).
Edit: I can not enter any AltGr key.
beppler commentedon Dec 4, 2019
After remove an older version of PSReadline eveything is working now.
sba923 commentedon Dec 4, 2019
FWIW, I have written the attached PowerShell scripts to verify what versions of PSReadline are on my system / which one is active.
CheckPSReadLineStatus.zip
HTH
hatvik commentedon Dec 13, 2019
To fix the same issue as beppler reported, do:
From elevated powershell Session do:
From elevated cmd session do:
powershell -noprofile -command "Install-Module PSReadLine -Force -SkipPublisherCheck -AllowPrerelease"ilmax commentedon Jan 15, 2020
What's the status of this issue?
Because looking at the linked issues it seems fixed, but it's still not working for me. In order to print the ~ character on an Italian keyboard layout, I'm used to do Alt+126 but this has a different behavior depending on the type of the terminal, but in none of them I'm able to get the ~ character printed, while doing directly in the the underlying shell (git/cmd/powershell/wsl not embedded in the windows terminal) works as expected
This is happening to me with the latest version of the windows terminal, at the moment of writing is:
lhecker commentedon Jan 15, 2020
Massimiliano Donini (@ilmax) I broke Alt+Numpad input in #3117. Now that #3117 had been merged and the associated issue been fixed, we could work on reintroducing numpad input into the code base.
I'd make this an optional, configurable behavior though, because I'm fairly certain that most potential users of the Terminal app won't benefit from it anymore. The app should thus default to sending all possible keyboard input to the shell so you can configure more advanced vim, etc. keybindings.
Implementing this should be a fair bit easier as soon as #4192 is merged. You'd have to add the additional logic right here and check whether the Alt key (and only the Alt key) is being held in
states, while the vkey stems from the numpad as opposed to from the regular numeric keys. Feel free to submit a PR at any time! 🙂ilmax commentedon Jan 15, 2020
Leonard Hecker (@lhecker) thanks for the quick response, I just wanted to know the state of this because every issue I found was closed but the problem is still there.
Not sure I'll come up with a PR on this, I never looked at the code before 😄 so I really don't know where to start, despite your suggestion.
I just wanted to know how to fix my workflow for git rebase -i because now I have to open something like notepad++, type the ~ character, copy it and paste it in the terminal.
DHowett-MSFT commentedon Jan 15, 2020
Just so I understand: you’re on a thread about AltGr with a question about alt+numpad sequences? This may be why all the threads you’re finding are closed: the AltGr problem is fixed.
I do believe we have a separate issue tracking alt+numpad input problems.
ilmax commentedon Jan 15, 2020
Yep, you're right, sorry for the confusion. I think #657 may the the correct one