Problem with color display after usage of unix "screen" command #556
Replies: 5 comments 3 replies
-
Definitely not an issue on your end, and also not on ours. I'll check the Windows Terminal issue list 😅 |
Beta Was this translation helpful? Give feedback.
-
I've ran into the same problem (I am also using windows terminal). Funnily enough, I've tried switching to oh-my-posh after I couldn't fix issues with https://github.com/justjanne/powerline-go that has text wrapping problems and duplicates prompt at times when the commands/entries in history got too long. So far I haven't noticed that in oh-my-posh (yay 🎉 ) but it didn't suffer from the screen problem. Not sure how similar the rendering engine is between the two. |
Beta Was this translation helpful? Give feedback.
-
Is there any fix for this? I am on WSL2 and trying to use OMP through "screen" from Windows Terminal |
Beta Was this translation helpful? Give feedback.
-
I have the same problem when using alacritty as terminal. The color of oh-my-posh have problem but the neofetch works well. I've tried the ANSI escape sequences. Basic colors works well but the true color mode can not show properly. It seems like the GNU Screen do not support the true color mode. |
Beta Was this translation helpful? Give feedback.
-
Any fix? |
Beta Was this translation helpful? Give feedback.
-
I followed the installation instructions on the documentation website both for my Windows machine (Windows Terminal) and Ubuntu server (version 20.04.2 LTS).
Yesterday everything worked fine. But today after I logged into my server and used the "screen" command the colors didn't get displayed correctly (see image below).
I'm using the Caskaydia Nerd Font.
Did I make a mistake or is this a bug?
(Splitted panes --> Left side: Ubuntu after login | Right side: Ubuntu after "screen" command)
Beta Was this translation helpful? Give feedback.
All reactions