PowerShell with oh-my-posh theme could not display u2500 and u2192 about pacmc HOT 14 CLOSED

If you update pacmc now, it uses a different arrow on Windows, because I just have no way to tell where it works and where it doesn't.
It is a workaround, but it improves the overall compatibility.

from pacmc.

🤔

from pacmc.

The download progress symbols look right for me even when using PowerShell:

from pacmc.

The arrow on the list command is not displayed correctly, but that is a Windows Terminal issue, sadly I can't do anything about 🤷‍♂️

from pacmc.

I don't know why I cannot display these symbol. (
Font: Droid Sans Slashed for Powerline, Consolas

from pacmc.

Your prompt seems to have some problems with special characters too

from pacmc.

It is oh-my-posh. Disable it will helps to solve this problem.

from pacmc.

Do you know whether I was right with my assumption that Windows Terminal is the reason for the arrow symbol (used by the pacmc list) command to not be displayed correctly?

Because in your last screenshot the arrow is there, but it isn't PowerShell running in the Windows Terminal either.

from pacmc.

Do you know whether I was right with my assumption that Windows Terminal is the reason for the arrow symbol (used by the pacmc list) command to not be displayed correctly?

Because in your last screenshot the arrow is there, but it isn't PowerShell running in the Windows Terminal either.

It is an third-party powershell plugin called “oh-my-posh” causing this problem.

from pacmc.

Yes but even without oh-my-posh it is still buggy in the new Windows Terminal, right?

from pacmc.

Yes but even without oh-my-posh it is still buggy in the new Windows Terminal, right?

No.

from pacmc.

I test and find out that using the theme by oh-my-gosh will cause this problem. I am using agnoster theme currently.
Update: I install and use DroidSansMono Nerd Font but problem still exist.

Update 2: I tested all of themes. All of them could not display these characters.

from pacmc.

Yes but it does not have anything to do with oh-my-posh or its themes I guess, it really seems to be a Windows Terminal problem.

I also had this problem without any PowerShell extension:
#12 (comment)
(the question mark should be an arrow)

from pacmc.

Yes but it does not have anything to do with oh-my-posh or its themes I guess, it really seems to be a Windows Terminal problem.

I also had this problem without any PowerShell extension:
#12 (comment)
(the question mark should be an arrow)

It works fine on my PowerShell.

from pacmc.