On Thu, Nov 13, 2014 at 01:27:29AM +0100, Manuel López-Ibáñez wrote:
> I think it is great that =auto becomes the default. However, adding a
> configure option for this seems overkill. If anyone really really
> wishes to change the default, they can simply edit a single-line in
> common.opt.
Configure option is what Richard asked me to do when changing the default,
and I think it is reasonable to give users a choice other than patching
the compiler (which is e.g. what I've been using in Fedora/RHEL for a year
or so now).
> Apart from that, I really cannot understand why someone would want the
> options none, auto or always: none is equivalent to auto-if-env but
> without the "if-env" escape route, and neither auto nor always allow
> disabling the coloring globally (which is precisely what users hating
That is not true. GCC_COLORS= in the environment (present and empty)
always disables colors, no matter what the -fdiagnostics-color= option
says (explicit or implicit). info gcc/man gcc documents this:
"Setting GCC_COLORS to the empty string disables colors."
auto-if-env is "never" if GCC_COLORS isn't in the environment, "auto"
if it is set to non-empty string, say
GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'
but even
GCC_COLORS=' '
will do and with GCC_COLORS= also disabled.
Jakub
