https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271
--- Comment #2 from Jan Niklas Hasse ---
I guess that's because one doesn't want the build output to depend on an
environment variable (most build systems won't rebuild on env variable
changes)?
-fdiagnostics-color doesn't affect the build outpu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271
Tyler Mace changed:
What|Removed |Added
CC||macetw at gmail dot com
--- Comment #3 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271
--- Comment #4 from Tyler Mace ---
The argument against environment variables doesn't make sense, when the
GCC_COLORS environment variables are used right within this feature.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271
Adam Borowski changed:
What|Removed |Added
CC||kilobyte at angband dot pl
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80271
--- Comment #7 from Eric Gallager ---
(In reply to Adam Borowski from comment #6)
> Created attachment 44260 [details]
> patch for CLICOLOR_FORCE
>
> So, here's a patch.
Please send patches to the gcc-patches mailing list for review.
