-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unicode observations on stdin & stdout #3786
Comments
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. |
I'm taking the baton here to find the dupes. Thanks @j4james for 1503. 😄 |
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! |
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:
The test steps were:
Run🏃
to the command prompt,The text was updated successfully, but these errors were encountered: