You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently set up a new computer with my standard dotfiles for the first time in a while and found that my custom section at the start of the prompt is no longer colored properly. Instead of setting the desired orange color, it just prints '166' before the lambda character.
Because the new computer was a Mac, I assumed it was due to some weirdness on that OS and opened a Q&A on the matter. I'll aim to put all relevant information here but here's the Q&A in case it's helpful: #1339
I found that on my Ubuntu 20.04 in WSL environment, pulling the latest version of the prompt caused the same issue to show up on the Windows Terminal. However, when I switched to the v3.16.7 tag the color came back, and going back to 4.0.0 returned it to the grey 166. So something in the 4.0.0 major release broke the color declaration I've been using.
I tried a few different ways of indicating the color and reordering my section so it's not the first item to no avail. I also tried changing dir.zsh to use my 166 color code and it went to the orange color with no problems, so I'm inclined to think that this is a bug and not a deliberate change in interpretation that hadn't been updated in the documentation.
The problem
I recently set up a new computer with my standard dotfiles for the first time in a while and found that my custom section at the start of the prompt is no longer colored properly. Instead of setting the desired orange color, it just prints '166' before the lambda character.
Because the new computer was a Mac, I assumed it was due to some weirdness on that OS and opened a Q&A on the matter. I'll aim to put all relevant information here but here's the Q&A in case it's helpful: #1339
I found that on my Ubuntu 20.04 in WSL environment, pulling the latest version of the prompt caused the same issue to show up on the Windows Terminal. However, when I switched to the v3.16.7 tag the color came back, and going back to 4.0.0 returned it to the grey 166. So something in the 4.0.0 major release broke the color declaration I've been using.
I tried a few different ways of indicating the color and reordering my section so it's not the first item to no avail. I also tried changing
dir.zsh
to use my 166 color code and it went to the orange color with no problems, so I'm inclined to think that this is a bug and not a deliberate change in interpretation that hadn't been updated in the documentation.Full zsh configs here: https://gitlab.com/SirDoctorK/dotfiles
Relevant Zsh configuration
What is version of Spaceship are you using?
4.13.3
What is version of Zsh are you using?
zsh 5.8 (x86_64-ubuntu-linux-gnu)
What operation system are you running?
MacOS 12.6.3, Ubuntu 20.04 (through WSL)
Do you use any Zsh framework or plugin manager?
oh-my-zsh
Which terminal emulator do you use?
Mac Terminal, Windows Terminal
Additional information
No response
The text was updated successfully, but these errors were encountered: