Clipboard with single character returns garbage via win32 interoperability

[am11]

This issue is also reproducible with MinGW64 and I am not sure what is the common denominator between WSL and MinGW. Please let me know if it belongs to a different repository / issue tracker.

:: get the OS version
C:\>ver

Microsoft Windows [Version 10.0.18298.1000]

:: enter some WSL distro
C:\>alpine

# get the OS version
~:❄️ $ cat /etc/os-release | grep VERSION
VERSION_ID=3.8.0

# test copy and paste using win32 interoperability
~:❄️ $ echo HelloWorld! | clip.exe; powershell.exe -noprofile -command Get-Clipboard
HelloWorld!

# test the same thing with single character to get weird character
~:❄️ $ echo 1 | clip.exe; powershell.exe -noprofile -command Get-Clipboard
਱

# same problem with an alphabet
~:❄️ $ echo a | clip.exe; powershell.exe -noprofile -command Get-Clipboard
੡

# with two or more characters, it works fine
~:❄️ $ echo A1 | clip.exe; powershell.exe -noprofile -command Get-Clipboard
A1

Get-Clipboard cmdlet or pasting with keyboard/mouse in any editor gives the same ੡ character.

[therealkenc]

Nice. Was able to reproduce here. No doubt this is an edge case in the two byte encoding on Windows and one byte WSL/Linux. Legit, thanks.

[therealkenc]

Try this. It's fun.

[therealkenc]

Forward dupe up to #4852 where there is some more investigation. The OP scenario is pretty clearly the same.

I am not sure what is the common denominator between WSL and MinGW

I am mildly sure. The common denominator between WSL and MinGW is clip.exe.

I can't reproduce the "echo a" game above on 19951. That could be #4637; we'll probably never know. Whatever that was, it is not related to the OP.

[sellithy]

Was this issue closed because it was fixed? If so, then it should be reopened because the same thing still happens.

[therealkenc]

/dupe #4852

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!