Encoding issues on pwsh 7.4 unfixable in Constrained Language Mode #5283
Unanswered
schaermu
asked this question in
Troubleshoot
Replies: 1 comment
-
This isn't solvable by you I suppose, you'll need to comment on that issue again and make them "solve" it. Or, downgrade PowerShell. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Code of Conduct
What happened?
After setting up pwsh 7.4 on my newly upgraded business laptop (got Windows 11 rolled out), i have issues getting the terminal to work. Starting up a properly configured Windows Terminal with a oh-my-posh profile looks like this:
While investigating, i found this issue mentioning several solutions to this issue:
[Console]::OutputEncoding = [Text.Encoding]::UTF8
into the $PROFILEIn my constrained enterpreise environment, neither of those solutions work:
OutputEncoding
is blocked byConstrainedLanguage
The only thing that works is pressing
CTRL+L
to clear the console, i have to do that after each and every command though...Printing
$OutputEncoding
tells me that utf-8 is already configured, i'm not sure that's true though...Seeing that this issue will not be fixed on PowerShells side (as the issue by @JanDeDobbeleer was closed), i'm trying to find other solutions / work-arounds. Not using oh-my-posh is a non-scenario ;)
Theme
easy-term
What OS are you seeing the problem on?
Windows
Which shell are you using?
powershell
Log output
Beta Was this translation helpful? Give feedback.
All reactions