Powershell: Dead key detection not working in PowerShell 7.0.0-preview.3

Created on 21 Aug 2019  路  7Comments  路  Source: PowerShell/PowerShell

Steps to reproduce

Install a multi layer keyboard layout like Neo2 and try to enter special caracters.

Expected behavior

Dead key detection should work properly for non-standard keyboard layouts.

The problem was already fixed in PSReadLine:
https://github.com/PowerShell/PSReadLine/issues/914

Actual behavior

There is an @ entered before the character. Apparently the current preview uses an old version of PSReadLine.

Environment data

PowerShell 7.0.0-preview.3

Issue-Question Resolution-Fixed

Most helpful comment

I think the latest preview is using the most recent PSReadLine release by default? @MovGP0 @uldisv can you check on the latest v7 preview?

All 7 comments

Another way to reproduce - install keyboard, that uses "dead keys" for accented characters (f.e. Latvian).
Pressing on a tilde (~), immediately produces @ sign.
Expected behaviour: depending on next pressed key - if again ~, then ~. Otherwise accented/diacritical letter.

/cc @daxian-dbw For information.

I think the latest preview is using the most recent PSReadLine release by default? @MovGP0 @uldisv can you check on the latest v7 preview?

I think the latest preview is using the most recent PSReadLine release by default? @MovGP0 @uldisv can you check on the latest v7 preview?

Works fine on Powershell 7.0 preview v.4 on Windows 10 x64.
Perfect - thank you.

@uldisv Please share PSReadline version. (Get-Module show this)

@uldisv Please share PSReadline version. (Get-Module show this)

ModuleType Version PreRelease Name
---------- ------- ---------- ----
Script 2.0.0 beta5 PSReadLine

Can confirm that it works in PowerShell 7.0.0-preview.4

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Michal-Ziemba picture Michal-Ziemba  路  3Comments

JohnLBevan picture JohnLBevan  路  3Comments

aragula12 picture aragula12  路  3Comments

andschwa picture andschwa  路  3Comments

alx9r picture alx9r  路  3Comments