Closed raulrm00 closed 2 years ago
Reading FAQ will fix this issue
@raulrm00 that's a limitation of PowerShell not being UTF-8. You can wraps the initialization in UTF-8 to resolve that:
$previousOutputEncoding = [Console]::OutputEncoding
try {
$OutputEncoding = [console]::InputEncoding = [console]::OutputEncoding = New-Object System.Text.UTF8Encoding
Initialize oh-my-posh here
} finally {
[Console]::OutputEncoding = $previousOutputEncoding
}
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?
If you have a Windows user with special characters in folder name, program can't be init with powershell config. Invoke-Expression calls will fail
Theme
all themes using default path could not be loaded
What OS are you seeing the problem on?
Windows
Which shell are you using?
powershell
Log output