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
When changing the console codepage utilizing [Console]::OutputEncoding, $OutputEncoding, or chcp.com to support unicode (codepage 65001) in the integrated console from my default codepage of 437, Get-Help breaks. All output is rendered improperly (powershell.exe is unaffected by these changes). If I try to use the More utility, it actually crashes.
Thanks for the report @TheIncorrigible1, this looks like another symptom of an encoding problem we've been meaning to look into in either the PowerShell host or the messaging layer.
I'm not aware of any workaround at the moment, but we'll look into it.
@BjornNordblom Thanks for the follow-up. After two years, significant changes have happened with the vscode terminal, but also this extension. I am also unable to recreate my steps above, but more.com still does not play nice with encodings being changed (though that's due to a bug with that particular application).
System Details
Issue Description
When changing the console codepage utilizing
[Console]::OutputEncoding
,$OutputEncoding
, orchcp.com
to support unicode (codepage 65001) in the integrated console from my default codepage of 437,Get-Help
breaks. All output is rendered improperly (powershell.exe
is unaffected by these changes). If I try to use theMore
utility, it actually crashes.Attached Logs
logs.zip
The text was updated successfully, but these errors were encountered: