News for hackers. Stuff that matters.
Re:Disabling ANSI color output by geocar on Wednesday February 07, 2018 @03:42AM (#16323085)
The comments on the homebrew merge request are incredibly frustrating to me, as the kind of insanity that can lead someone to think there are only four programs that offer an ability to disable colours is something I thought I escaped by avoiding Facebook.

Here's the workaround I use:

    brew() { /usr/local/bin/brew "$@" | cat; }
Re:Disabling ANSI color output by tym0 on Wednesday February 07, 2018 @08:31AM (#16324220)
The rejection is not about the ability to disable colours but about adopting a "standard" that someone made up by themselves.
Re:Disabling ANSI color output by geocar on Wednesday February 07, 2018 @05:50PM (#16328699)
> The rejection is not about the ability to disable colours

That's all the code does.

> … but about adopting a "standard" that someone made up by themselves.

People's imagination is where standards come from.

People make them up and get agreement from other people to implement them.

Re:Disabling ANSI color output by khedoros1 on Thursday February 08, 2018 @12:03AM (#16330324)
On one level the code allows disabling color with a flag. On another level, the code provides support for a nascent attempt at creating a new standard.

Software development is a social activity, and if someone wants to introduce new functionality, they have to convince others that it's a desirable change. Making up a "standard" is the easy part; I'd expect that convincing others to adopt it is more challenging.