Open echarlie opened 1 month ago
@flatcap did a big overhaul of the colour-handling code. He'll be able to comment when he's back from vacation :)
yup. I had to dig through the changelog. my workaround is just to set sensible background and foreground colours for indicator so I can at least read my email, but it's kinda ugly. I'd like to see a solution where "merge colours" and "use terminal foreground/background" are different directives, because I do see utility of merging all the colours together (the new behaviour).
Thanks - unfortunately I can't comment on that, my knowledge of the whole color merging logic is nil.
Some context already: https://github.com/neomutt/neomutt/issues/4095#issuecomment-1792748431
About 18 months ago, I made default mean transparent, everywhere. The recent colour refactoring made the checking a bit stricter.
in releases prior to 2022-04-15
default
means the terminal background colour is used, as described in older versions of the f1 documentation:Thus, my colour config looked like
Expected Behaviour
My terminal (urxvt) has pseudo-transparency configured in xorg. i.e. my xresources had
This can also be reproduced if
*.background
is not also in the colour pallete.Prior to 2022-04-15 release (i.e. when I was on debian bullseye and earlier), the
default
keyword used the terminal background, rather than merging multiple colour descriptionsActual Behaviour
colours get merged. thus
results in yellow on yellow for a New message with the cursor (unreadable), rather than yellow on terminal background.
Steps to Reproduce
set a non-standard terminal background colour. test above colour samples on releases before/after the 2022-04-15 version.
How often does this happen?
When did it start to happen?
NeoMutt Version
Extra Info