No_color

> Why not just set $TERM to dumb or xterm without color support? Or change all color definitions in the terminal to print the same color? > The terminal is capable of color and should be able to print color when instructed. NO_COLOR is a hint to the software running in the terminal to suppress addition of color, not to the terminal to prevent any color from being shown. I have to admit I don't really get this. I personally…

> If your software outputs color by default, please consider not doing so. Quite opinionated for not giving additional 𝘃𝗮𝗹𝗶𝗱 arguments. Also the arguments regarding colorblind crowd being unable to distinguish colors are weak, as accessibility best practices suggest to convey semantically relevant markup and content in multiple sensory means, so that everybody has their chance to understand it (e.g. setting links in a distinguished color and underlined). Using colors (e.g. rkhunter malware report with its hundreds…

Hmm, why not. Though most of the software do the right thing by checking if the standard output is an actual tty (isatty) to avoid colors when redirecting to something else (e.g. socket, fifo, etc). The name NO_COLOR suggests a really binary choice which may be okay. Though GNU coreutils usually have a more selective option like --color=always|auto|never. I'd prefer supporting a more general COLORS=on|off|compatible|... Meaning: - on: always on even when redirecting - off: fully off - compatible: maybe…

In the meantime, I have a janky (s)trip (c)olor function in my .bashrc to help with this: function sc { sed "s,$(printf '\033')\\[[0-9;]*[a-zA-Z],,g" }