Unicode observations on stdin & stdout

[sipsorcery]

It's nice to see that unicode handling on stdin and stdout is improving from the old Windows Console.

The tests below were done using:

• Windows 10 Pro 10.0.1.19033 Build 19033
• Windows Terminal Preview v0.7.3291.0
• Font: cascadia

The test steps were:

1. Paste Run🏃 to the command prompt,
2. Hit Enter
3. Press the Up Arrow

[j4james]

I suspect there may be two separate issues here, because each shell has its own command line editor. For PowerShell, this problem was previously reported in issue #1503. For the cmd shell, I think it's a limitation of the COOKED_READ implementation, and the way it handles surrogate pairs. I couldn't find an existing issue for that, but it's possible it could be addressed by #780.

[DHowett-MSFT]

I'm taking the baton here to find the dupes. Thanks @j4james for 1503. 😄

[zadjii-msft]

You know, he never did find those dupes 😛

I'll go with #1503 since that's basically the root cause here. Thanks! /dup #1503

[ghost]

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