This is the mail archive of the
mailing list for the GCC project.
Re: diag color
- From: Markus Trippelsdorf <markus at trippelsdorf dot de>
- To: phi gcc <phi dot gcc at gmail dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 31 Jul 2016 08:25:39 +0200
- Subject: Re: diag color
- Authentication-results: sourceware.org; auth=none
- References: <CADieKzu2BhHBTzhWrQjuCCZixd7bnq2syB=z+8JvXbeFL2L6FQ@mail.gmail.com>
On 2016.07.31 at 08:08 +0200, phi gcc wrote:
> Hi All,
> Reposting this here from gcc-help.
> I got the impression that I got colors in diag output depsite the fact
> that I got no GCC env var setup.
> The version I used is
> CX08$ cc --version
> cc (Ubuntu 5.4.0-6ubuntu1~16.04.1) 5.4.0 20160609
> This is a bit of a problem because I don't use an xterm, and the term
> I used don't understand vt100 (xterm, etc..) escape sequence.
> my TERM env var is properly setup, emacs etc all works with my TERM
> and terminfo database that define how to do colors.
> Would it be posible that gcc honors the TERM variable setup, if using
> termcap/terminfo is too complicated, at least disable coloring if TERM
> is not vt100 compatible.
Well, the current setup works for the vast majority of users.
You can either use -fno-diagnostics-color in your CFLAGS or configure
gcc with: --with-diagnostics-color=never.