Open jgcodes2020 opened 2 years ago
It's not actually a bug; the parsing/interpretation is compatible with https://linux.die.net/man/3/xparsecolor which explicitly defines the behavior this way.
We're compatible with xparsecolor so that we match xterm's behavior when processing true color escapes.
Closing this as "working as intended".
Needs docs
What Operating System(s) are you seeing this problem on?
Linux Wayland
WezTerm version
wezterm 20220317-165235-27088fab
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
I first observed this bug using neofetch, while copying my GNOME Terminal color scheme to WezTerm. In WezTerm, the color bright red (configured to
This is the same colour in GNOME Terminal:
![image](https://user-images.githubusercontent.com/35639051/159092223-9b507bbf-11dc-4ace-8255-8004396beb12.png)
#F55
) yields this:If you look closely, you'll notice that the colour in GNOME Terminal is a bit brighter.
To Reproduce
Using my config file, run the following:
Configuration
Expected Behavior
Wezterm takes
#F55
to mean#F05050
, when other terminals (and web browsers) will use#FF5555
.Logs
Anything else?
No response