As long as CLI programs stick to the 8 or 16 standard colors and refrain from setting background colors (inverse mode is fine), as well as from explicitly setting white or black as text color, everyone can reasonably configure their terminal colors so that everything is readable.

When going beyond that, the colors really need to be configurable on the application.

▲

JohnLeitch 6 hours ago | parent | next [-]

> refrain from setting background colors

That's the thing though, setting bg color opens up a lot of options, and constraining to invert is not sufficient in my opinion.

	▲	reactordev an hour ago \| parent \| next [-]
		Sticking to the \x1b[4X background color is probably safe as that can be tweaked by terminal color palettes. It’s when you use the 256 or RGB \x1b codes that it becomes an issue. Ok for foreground.
	▲	layer8 4 hours ago \| parent \| prev \| next [-]
		That’s fine, but please make the colors configurable then. For example like Mutt does: http://www.mutt.org/doc/manual/#color
	▲	Joker_vD 6 hours ago \| parent \| prev [-]
		> constraining to invert is not sufficient in my opinion Eh. Doing green/red text color with default background, maybe inverted works amazing for me. In fact, I'd say that every sensible colour scheme for a terminal should have as the default foreground/background colours something that is more or less contrasting against every other explicitly named colour, including black and white (I personally have #212121 on #EEEEEE).

▲

Arch-TK 4 hours ago | parent | prev [-]

Configurable within the application... at runtime.

I want to be able to switch existing terminals with existing applications between themes.