public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pva at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/36150] colorize output of gcc
Date: Tue, 06 May 2008 18:08:00 -0000 [thread overview]
Message-ID: <20080506180748.1332.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36150-14488@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from pva at gentoo dot org 2008-05-06 18:07 -------
Andrew, it's very pity to see this bug closed as invalid so fast. Besides being
useful, people enjoy colors and people work with compilers...
I've already stated that, but I repeat. colorgcc does not work in case you have
localized output (see our bug report). Reading source of colorgcc it seems that
it uses words like "warning" or error as a key to parse and colorize output.
Thus taking into account the number of human languages gcc is translated to and
will be in future, adding complexity of having different encodings leaves
colorgcc hardly working without "fixing it with rasp-file" after translation
updates or additions. The complexity of this makes me think that it's natural
to have this feature in place where error/warning is thrown - that is in gcc
itself...
bug 36150 although could help, as it makes possible to parse error based on
numbers, works only for languages with stable "references" where it's hardly
possible that numbers changes, as in other case wrong coloring could mislead
programmer...
Summarizing, I do not see why decision error or warning we have should be
decided based on output after gcc and not in first place - in gcc itself -
where it's known with high certainty.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150
next prev parent reply other threads:[~2008-05-06 18:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 9:36 [Bug other/36150] New: " pva at gentoo dot org
2008-05-06 15:28 ` [Bug other/36150] " pinskia at gcc dot gnu dot org
2008-05-06 17:28 ` esigra at gmail dot com
2008-05-06 17:35 ` pinskia at gcc dot gnu dot org
2008-05-06 17:38 ` pinskia at gcc dot gnu dot org
2008-05-06 18:08 ` pva at gentoo dot org [this message]
2008-05-06 18:41 ` esigra at gmail dot com
2008-05-06 21:29 ` brian at dessent dot net
2008-05-06 21:56 ` esigra at gmail dot com
2008-05-06 21:58 ` pinskia at gcc dot gnu dot org
2008-05-06 22:07 ` brian at dessent dot net
2008-05-07 6:55 ` pva at gentoo dot org
[not found] <bug-36150-4@http.gcc.gnu.org/bugzilla/>
2010-10-02 17:04 ` pinskia at gcc dot gnu.org
2010-10-02 17:52 ` manu at gcc dot gnu.org
2010-10-02 19:51 ` manu at gcc dot gnu.org
2011-03-16 14:49 ` manu at gcc dot gnu.org
2013-04-14 17:57 ` manu at gcc dot gnu.org
2014-01-20 2:41 ` bluetooth.developer at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080506180748.1332.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).