JanDeDobbeleer / oh-my-posh

The most customisable and low-latency cross platform/shell prompt renderer
https://ohmyposh.dev
MIT License
17.38k stars 2.38k forks source link

Not compatible with pwsh 7.2 #1216

Closed bravoeguizabal closed 2 years ago

bravoeguizabal commented 2 years ago

Code of Conduct

What happened?

This is what it looks like when using powershell 7.1.5 pwsh7 1 5 Then right after upgrading to powershell 7.2.0 the glyphs seem to be working but the colors are not there anymore. pwsh7 2 0 Any ideas what might have happened?

Btw, awesome work putting together this package @JanDeDobbeleer!

Version

6.2.3

Theme

paradox

What OS are you seeing the problem on?

Windows

Which shell are you using?

powershell

Relevant log output

No response

JanDeDobbeleer commented 2 years ago

@bravoeguizabal that's going to be something else than 7.2 (or oh-my-posh). We also just received a neat screenshot from another user on 7.2.0 and here's my config (both on macOS and Windows):

image image

Can you share your $PROFILE and config (if it's default, pls ignore)?

bravoeguizabal commented 2 years ago

This is my profile:

Import-Module posh-git Import-Module oh-my-posh Set-PoshPrompt -Theme paradox

config is just the default

I upgraded to 6.2.5 but am getting the same result. I tried to check if something in my environment is interfering with oh-my-posh but can't thing of anything.

JanDeDobbeleer commented 2 years ago

@bravoeguizabal this is interesting. Can you have a look at what $PSStyle.OutputRendering says? That should be ANSI.

bravoeguizabal commented 2 years ago

Currently that field is set to: OutputRendering : Host

JanDeDobbeleer commented 2 years ago

@bravoeguizabal try setting that to ANSI and maybe also have a look at any of these.

bravoeguizabal commented 2 years ago

Jan, thanks for the links you shared I got the clue from there. It happens that I was setting TERM to a dumb value in my environment therefore the lack of color. I removed that from my environment and now I have my posh shell working perfectly. Sorry about that! Looks like $Env;TERM doesn't have any effect on previous versions of pwsh but the latest.

github-actions[bot] commented 7 months ago

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.