[Bug other/36150] colorize output of gcc

2014-01-19 Thread bluetooth.developer at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150 bluetooth.developer at gmail dot com changed: What|Removed |Added CC||bluetooth.developer

[Bug other/36150] colorize output of gcc

2013-04-14 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150 Manuel López-Ibáñez changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #16 from Manuel

[Bug other/36150] colorize output of gcc

2011-03-16 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150 --- Comment #15 from Manuel López-Ibáñez 2011-03-16 14:41:50 UTC --- More users trying to get this feature by parsing the output of GCC (which is not meant to be machine-readable): http://www.mixtion.org/gccfilter/

[Bug other/36150] colorize output of gcc

2010-10-02 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150 --- Comment #14 from Manuel López-Ibáñez 2010-10-02 19:51:34 UTC --- For future reference, more examples of color diagnostics in clang can be found here: http://llvm.org/devmtg/2009-10/StateOfClang.pdf but that is quite old, recent clang versio

[Bug other/36150] colorize output of gcc

2010-10-02 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150 --- Comment #13 from Manuel López-Ibáñez 2010-10-02 17:52:39 UTC --- Somehow I missed this bug when searching. For those here in favour of color, clang has it and people love it [*]. Luckily, this is one of those clang things that can be done in

[Bug other/36150] colorize output of gcc

2010-10-02 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150 Andrew Pinski changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Comment #12 f

[Bug other/36150] colorize output of gcc

2008-05-06 Thread pva at gentoo dot org
--- Comment #11 from pva at gentoo dot org 2008-05-07 06:54 --- (In reply to comment #9) > The other issue here is that people want different colors for each of their > warnings so why hardcode it. It should be easy to make this configurable... Well I've googled a bit and did not found

[Bug other/36150] colorize output of gcc

2008-05-06 Thread brian at dessent dot net
--- Comment #10 from brian at dessent dot net 2008-05-06 22:06 --- Subject: Re: colorize output of gcc esigra at gmail dot com wrote: > printf("%s%s%s%s", warning_format_start, _("warning: "), _("the actual > message"), warning_format_end); But then that is not simply "adding a colou

[Bug other/36150] colorize output of gcc

2008-05-06 Thread pinskia at gcc dot gnu dot org
--- Comment #9 from pinskia at gcc dot gnu dot org 2008-05-06 21:58 --- The other issue here is that people want different colors for each of their warnings so why hardcode it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150

[Bug other/36150] colorize output of gcc

2008-05-06 Thread esigra at gmail dot com
--- Comment #8 from esigra at gmail dot com 2008-05-06 21:55 --- (In reply to comment #7) > If you added escape sequences to the string constants in the gcc source > then it would only work for the C locale messages. Adding escape sequences for colours would work as well with localizati

[Bug other/36150] colorize output of gcc

2008-05-06 Thread brian at dessent dot net
--- Comment #7 from brian at dessent dot net 2008-05-06 21:28 --- Subject: Re: colorize output of gcc esigra at gmail dot com wrote: > And seriously, what is more efficcent, adding a > colour code sequence to the string constans in GCC that says "warning:", > "error:" etc or having a

[Bug other/36150] colorize output of gcc

2008-05-06 Thread esigra at gmail dot com
--- Comment #6 from esigra at gmail dot com 2008-05-06 18:40 --- (In reply to comment #4) > I rather not add too much complexity to gcc diagnostic output. Which means > no color. We did not demand that you do it personally. We just think that it would be a really good idea if someone

[Bug other/36150] colorize output of gcc

2008-05-06 Thread pva at gentoo dot org
--- 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 lo

[Bug other/36150] colorize output of gcc

2008-05-06 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2008-05-06 17:37 --- I rather not add too much complexity to gcc diagnostic output. Which means no color. colorgcc could be extended to get the correct coloring for the locazation. See also http://gcc.gnu.org/bugzilla/show_bug.cgi?i

[Bug other/36150] colorize output of gcc

2008-05-06 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2008-05-06 17:35 --- http://schlueters.de/colorgcc.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150

[Bug other/36150] colorize output of gcc

2008-05-06 Thread esigra at gmail dot com
--- Comment #2 from esigra at gmail dot com 2008-05-06 17:27 --- I would definitely like GCC to produce colourized output. It can really improve the readability. I miss that feature. It has my vote. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150

[Bug other/36150] colorize output of gcc

2008-05-06 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-05-06 15:28 --- I don't think we should do this. There is already a secondary program that does the coloring too. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36150