Hi!
gcc 4.8.0-6.fc19 and later contains a backport of color diagnostics
support from gcc trunk. Right now it is disabled by default, unless GCC_COLORS
env var is set in the environment (to non-empty value), and
-fdiagnostics-color={never,auto,always} switch can be used to override this
(never is
Jakub Jelinek wrote:
Would users appreciate it being done by default (i.e. make
-fdiagnostics-color=auto the default)?
Could you give a little more information?
* What is gcc diagnostic colors exactly?
* Any pros/cons?
-- rex
--
devel mailing list
devel@lists.fedoraproject.org
On Mon, May 27, 2013 at 10:29:56AM -0500, Rex Dieter wrote:
Jakub Jelinek wrote:
Would users appreciate it being done by default (i.e. make
-fdiagnostics-color=auto the default)?
Could you give a little more information?
* What is gcc diagnostic colors exactly?
Colorized output of gcc
gcc 4.8.0-6.fc19 and later contains a backport of color diagnostics
support from gcc trunk. ...
Would users appreciate it being done by default (i.e. make
-fdiagnostics-color=auto the default)?
* Any pros/cons?
Same thing as pros/cons of colorizing grep or ls output by default.
Let's
On 05/27/2013 06:16 PM, John Reiser wrote:
gcc 4.8.0-6.fc19 and later contains a backport of color diagnostics
support from gcc trunk. ...
Would users appreciate it being done by default (i.e. make
-fdiagnostics-color=auto the default)?
* Any pros/cons?
Same thing as pros/cons of
On Mon, May 27, 2013 at 10:16:56AM -0700, John Reiser wrote:
Let's make an explicit list. Here is a start:
0. Supposedly the colors provide faster visual communication, increased ease
of recognition and understanding, etc.: an enhancement.
Yeah, that is the goal.
1. Background color
