You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't spent much time on non-English keyboard layouts, there are definitely some differences with these bindings on a French layout.
You might find a workaround by binding things directly via Set-PSReadlineKeyHandler, but it might take some fiddling, e.g. the shift state for a period is different between English and French keyboards. In other cases, the scan code is different (as is the case for '?'), that might be the source for the other problems.
Activity
lzybkr commentedon Oct 13, 2014
The language version of Windows shouldn't matter
I haven't spent much time on non-English keyboard layouts, there are definitely some differences with these bindings on a French layout.
You might find a workaround by binding things directly via Set-PSReadlineKeyHandler, but it might take some fiddling, e.g. the shift state for a period is different between English and French keyboards. In other cases, the scan code is different (as is the case for '?'), that might be the source for the other problems.
kayasax commentedon Oct 15, 2014
maybe you can provide an xml file to adapt the default keybinding based on the langage/keyboard layout ?
lzybkr commentedon Oct 31, 2017
I believe this is fixed in #561.
I'll publish a pre-release version to the PowerShell Gallery as soon as they support pre-releases.
If you'd like to try a fix before that, you can build the lastest yourself from the master branch, or
grab a build from AppVeyor like this one.
Note the version number is now 2.0, so be sure to copy the contents to \PSReadLine\2.0.
lzybkr commentedon Nov 4, 2017
I'll have an official prerelease build out next week if you want to verify this is fixed, otherwise you can grab a build out of appveyor here.