Closed xantari closed 11 months ago
@JanDeDobbeleer I created this issue at PowerShell as they need to fix this. The problem with moving the entire shell to UTF8 is that it has other annoying side effects depending on the locale and encoding of your machine (Windows quirk). I can add this to the FAQ, but with a huge warning statement.
Gotcha, thanks as always for the prompt replies!
Also fixed by setting Administrative Language Settings > Administrative > Change System Locale > Beta: Use Unicode UTF-8 for worldwide language support. I guess that's about the same as changing it in your profile.
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.
Code of Conduct
What happened?
When using Oh My Posh, which was successfully working just fine with Powershell 7.3.10, after upgrading to 7.4.0 all text becomes unreadable. See here for example:
The fix it turns out was here: https://github.com/PowerShell/PowerShell/issues/19941
The key part being [Console]::OutputEncoding = [Text.Encoding]::UTF8
After implementing that fix, it works correctly:
I am not sure if this is something that Oh My Posh can accomidate without doing the above "work around" or if the documentation now needs to be updated to indicate this line is now required with Powershell 7.4.0 and beyond: [Console]::OutputEncoding = [Text.Encoding]::UTF8
Theme
Atomic
What OS are you seeing the problem on?
Windows
Which shell are you using?
powershell
Log output