[cfe-dev] Colorized compiler errors

[Chris Lattner]

On Dec 22, 2007, at 12:20 PM, Shantonu Sen wrote:
> Seems like it would have to be significantly more complex to know what
> escape sequences to use (eg by looking at $TERM).

The policy decisions can be made when the code exists :).  It seems  
straight-forward to require users to set an envvar to get it or  
something, like the mono people did.

> Also, IDEs would probably want to disable colors even if they run the
> compiler hooked up to a pty, in favor of a builtin compiler neutral
> colorizer.

This would only exist in the console-output diagnostics  
implementation.  An IDE would use a separate implementation: we don't  
expect an IDE to be "parsing" the error/warning output of the  
compiler, it would just use the diagnostics reporting API natively.

-Chris

>
> Sent from my iPhone
>
> On Dec 22, 2007, at 11:08 AM, Keith Bauer <onesadcookie at gmail.com>
> wrote:
>
>>> And how will you solve it in a portable manner?
>>
>> #if !defined(_WIN32) // ideally a more robust configure-based test
>>   if (isatty(STDOUT_FILENO))
>>
>> ;)
>>
>> -Keith
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev