PSReadLine: Win7: Cyrillic input with shift partially does not work
Environment data
PS version: 5.1.14409.1012
PSReadline version: 2.0.0-beta3
os: 6.1.7601.17514 (win7sp1_rtm.101119-1850)
PS file version: 10.0.14409.1005 (rs1_srvoob.161208-1155)
Steps to reproduce or exception report
Installed latest PSReadline under PSv5.1 / Win7
switch keyboard to russian input, type:
- without shift -
йцукенгшщзхъ
- should be (without shift but with caps) -
ЙЦУКЕНГШЩЗХЪ
- with shift only -
ЦУШЩХЪ
- with caps + shift -
цукшщхъ
and many other symbols got eaten too
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 15 (10 by maintainers)
Commits related to this issue
- Remove Keys.ShouldInsert The method Keys.ShouldInsert was a misguided attempt to avoid inserting keys where there is no binding but the key really doesn't make sense as input. Unfortunately it is ju... — committed to PowerShell/PSReadLine by lzybkr 6 years ago
- Remove Keys.ShouldInsert (#822) The method Keys.ShouldInsert was a misguided attempt to avoid inserting keys where there is no binding but the key really doesn't make sense as input. Unfortunate... — committed to PowerShell/PSReadLine by lzybkr 6 years ago
I’m on 2004 build and still not fixed, PSReadLine version is still 2.0.0 I had to update it manually, and bug is gone Run this line in PowerShell from administrator:
Install-Module PSReadLine -force
#822 fixes just the problem initially reported here.
The rendering of
?
(and it’s just a rendering problem, the characters are correct if executed) was introduced by #771, the workaround for now is to run:There is one additional problem if you start PowerShell with the Cyrillic keyboard - PSReadLine will fail to load, and the only workaround right now is to start PowerShell with a different keyboard.
@SteveL-MSFT These is very annoying. Can you share information when fixes is expected for Windows?
We also face this issue on Windows 10 (1809) Version: 10.0.17763 Build 17763.
Preinstalled powershell module PSReadLine verison is 2.0.0
Here’s a link to discussion on technet: https://social.technet.microsoft.com/Forums/ru-RU/8ccdf213-56ca-461e-8ce1-0cc82391dddb/windows-10-1809-10551088108610731083107710841099-1089
The problem exist with EN-US keyboard layout selected on powershell console start. With Cyrillic keyboard layout (RU-RU) select problem doesn’t reproduced, `cause module PSReadLine probably doesn’t load properly.