PS version: 7.0.0
PSReadline version: 2.0.0
os: 10.0.18362.718 (WinBuild.160101.0800)
PS file version: 7.0.0.0
HostName: ConsoleHost
BufferWidth: 120
BufferHeight: 9001
Press Ctrl+r
Start searching in command history
<泻> symbol appears (Russian letter 泻)
this behavior does not depend on the selected keyboard layout
also all the keyboard shortcuts with Ctrl lead to the appearance of Russian characters.
For example, pressing Ctrl + v displays the Russian character <屑>.
And this behavior does not depend on the selected keyboard layout.
@Sublihim The issue template contains a script. Please run the script and add the script output to the issue description.
@iSazonov In the _environment_ template?
I started it.
Duplicate the output below:
PS version: 7.0.0
PSReadline version: 2.0.0
os: 10.0.18362.718 (WinBuild.160101.0800)
PS file version: 7.0.0.0
HostName: ConsoleHost
BufferWidth: 120
BufferHeight: 9001
this behavior does not depend on the selected keyboard layout
@Sublihim What do you mean by this? Aren't you using the Russian keyboard layout? How can I reproduce this?
I can not repo on 10.0.17763.1039 with Russian keyboard layout. We need more info.
The error is reproduced regardless of the layout (Russian or English)
In fact, I realized it looks like this error: https://github.com/PowerShell/PSReadLine/issues/1393
If I run PowerShell at The moment when the system is switched to the English layout, then everything works well.
@Sublihim Please share more info. Is your system installed from Russian or English distributive? If English do you install language pack? What is default for non-unicode programs? What is other region and language options? What is default keyboard layout? Do you use Windows Terminal?
Can you share screenshots? and maybe an animation with repo?
This is reproduced on both the Russian-language distribution and the English-Language distribution with Russian-Language pack installed.
Thanks! Looks like this is a key here.
Thanks @Sublihim for the additional information!
Indeed, this looks resulted by the same root cause of #1393. I will resolve this issue as a duplicate of the other one.
Most helpful comment
Thanks! Looks like this is a key here.