Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

A lot of oh-my-posh users are reporting issues with incorrect prompt rendering since the upgrade to 7.4. On our end, nothing changed in that area and I'm unable to reproduce this myself. What we do know is that changing the encoding overall to UTF8 solves the issue, which is why we're thinking in that direction. It's also only for icons in a specific range apparently.

Doesn't work:

oh-my-posh init pwsh --config ~/custom.omp.json | Invoke-Expression

Works:

[Console]::OutputEncoding = [Text.Encoding]::UTF8
oh-my-posh init pwsh --config ~/custom.omp.json | Invoke-Expression

Expected behavior

It displays the prompt without issues

Actual behavior

You can see garbled text

Error details

Not applicable

Environment data

$PSVersionTable
Name
Value
PSVersion
7.4.0
PSEdition
Core
GitCommitId
7.4.0
OS
Microsoft Windows 10.0.22000
Platform
Win32NT
PSCompatibleVersions
4.0....)
{1.0, 2.0, 3.0, 4.0....®
PSRemotingProtocolVersion
2.3
SerializationVersion
1.1.0.1
WSManStackVersion
3.0

Visuals

Linked issues:

• https://discord.com/channels/1023597603331526656/1176109431382081546
• FiraCode NF Icons not rendering JanDeDobbeleer/oh-my-posh#4475 (pwsh 5, but same issue so could also be related to PSReadline perhaps?)
• Strange Font Issue JanDeDobbeleer/oh-my-posh#4468
• Encoding issues after using Powershell 7.4.0 JanDeDobbeleer/oh-my-posh#4499
• Powershell 7.4\.5 will not render Nerd Fonts Glyphs correctly. JanDeDobbeleer/oh-my-posh#5665
• Windows PowerShell works, pwsh 7.4.5 doesn't JanDeDobbeleer/oh-my-posh#5662