Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PowerShell with oh-my-posh theme could not display u2500 and u2192 #12

Closed
WordlessEcho opened this issue Jul 14, 2021 · 14 comments
Closed

Comments

@WordlessEcho
Copy link

image
Looks good in cmd.exe:
image

@WordlessEcho
Copy link
Author

🤔
image

@jakobkmar
Copy link
Owner

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

@jakobkmar
Copy link
Owner

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

grafik

@WordlessEcho
Copy link
Author

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

image

@jakobkmar
Copy link
Owner

jakobkmar commented Jul 14, 2021

Your prompt seems to have some problems with special characters too

@WordlessEcho
Copy link
Author

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

@jakobkmar
Copy link
Owner

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.

@WordlessEcho
Copy link
Author

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.

@jakobkmar
Copy link
Owner

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

@WordlessEcho
Copy link
Author

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

No.

@WordlessEcho
Copy link
Author

WordlessEcho commented Aug 6, 2021

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.
image

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

@WordlessEcho WordlessEcho changed the title PowerShell could not display u2500 and u2192 PowerShell with oh-my-posh theme could not display u2500 and u2192 Aug 6, 2021
@jakobkmar
Copy link
Owner

jakobkmar commented Aug 6, 2021

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)

@WordlessEcho
Copy link
Author

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.
image

@jakobkmar
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants