This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c/45850] support color diagnostics


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45850

--- Comment #8 from Gabriel Dos Reis <gdr@integrable-solutions.net> 2010-10-02 18:41:28 UTC ---
On Sat, Oct 2, 2010 at 1:30 PM, manu at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45850
>
> --- Comment #6 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2010-10-02 18:30:45 UTC ---
> (In reply to comment #4)
>> On Sat, Oct 2, 2010 at 11:59 AM, manu at gcc dot gnu.org
>>
>> IDEs let users get the colors they want -if they ever wanted.
>
> The output of GCC is not designed to be parsed by IDEs:
>
> http://gcc.gnu.org/PR19165
>
> nor is GCC designed to be tightly integrated with an IDE.

that PR is a proof of what?

One reason we have standardized on 'warning: ', 'error: ', etc.
prefixes is precisely so that IDEs or other tools can differentiate
them.  The fact that we have not succeeded in many other areas
is more of a shortcoming than a design goal.

>> (the above is certainly a wrong default for me -- the background
>> of my terminal is always dark. :-)
>
> It is readable in my black background. It also looks nice here:

I think we may just have found two sets of people who disagree
on what is readable with a dark background.  Which is precisely
the point of my original message.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]