@nixCraft Actually there is not even a need to disable color by default: Colors only cause trouble when working with pipes and redirections. Whether a program is writing to a terminal or to a pipe can trivially checked by calling istty().

These people complaining are bullies. We should ban them from our communities.

@nixCraft I'm one of those people who really really dislikes colour in console output. It makes everything harder to read, especially in a terminal with a dark background. Syntax highlighting is usually one of the first things I turn off in text editors too.

I don't yell at the developers or anything (as long as there is an option to disable it), but it irks me when they enable stuff like that by default.

@nixCraft

Ire strongly correlates with whether the program

• respects $NO_COLOR¹

• behaves properly when isatty() vs when piped to a subsequent program

• properly consults termcap/terminfo, respecting terminals other than VT100 or xterm-color

⸻
¹ https://no-color.org/

@nixCraft I have no idea. Personally I love a colored terminal and I think a lot of other people do, too, given that it's the default in a lot of distributions.

Just gotta ignore the haters.

@nixCraft I don’t yell when the option is added.

I holler into the ether when the previously new option is now the default.

@nixCraft isually the color goes away witch appending

| cat

"the cat ate the colors"

@nixCraft

I find it on by default too many times. Often color blind unfriendly colors. Often makes assumptions about other external factors (dark versus light mode).

Environment variables or command line options don't scale well. New commands adding stuff need to be tracked and whacked. Using large numbers of systems becomes difficult without full configuration management.

If you need fancy visual effects you might want a GUI.

#Linux #Unix