Closed antonklimov closed 2 years ago
@antonklimov two things you can try:
$PROFILE
: [console]::InputEncoding = [console]::OutputEncoding = [System.Text.UTF8Encoding]::new()
That worked, thanks, and in the meantime it was already 7.13.0, but then on a restart I have the same problem again,
The fix should stay persistent unless the profile wasn't saved somehow?
Finally I have it working, maybe profile was not persisting. I also had problems because I am using both core and desktop versions of powershell. I think currently they are fighting each other like I upgraded one and then when starting the other it downloaded the older executable. I think ideally since the modules are installed separately in core and desktop the executable should not be shared somehow.
@antonklimov yes, core and 5 do not share the same modules and 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?
Updating oh-my-posh executable to 7.12.0 Downloading oh-my-posh themes for 7.12.0
Action to take for this exception: Program 'oh-my-posh.exe' failed to run: StandardOutputEncoding is only supported when standard output is redirected.At C:\Users\aklimov\Documents\PowerShell\Modules\oh-my-posh\7.12.0\oh-my-posh.psm1:158 char:6
Theme
custom
What OS are you seeing the problem on?
Windows
Which shell are you using?
No response
Log output