colors in gdc errors

[Iain Buclaw]

On Oct 1, 2013 12:50 PM, "eles" <eles at eles.com> wrote:
>
> On Tuesday, 1 October 2013 at 11:47:31 UTC, eles wrote:
>>
>> On Tuesday, 1 October 2013 at 09:57:38 UTC, Iain Buclaw wrote:
>>>
>>> On Oct 1, 2013 8:20 AM, "eles" <eles at eles.com> wrote:
>>>>
>>>>
>>>> On Tuesday, 1 October 2013 at 03:36:09 UTC, Iain Buclaw wrote:
>>>>>
>>>>>
>>>>> On 3 September 2013 17:03, Iain Buclaw <ibuclaw at ubuntu.com> wrote:
>>>>>>
>>>>>>
>>>>>> On 3 September 2013 16:54, eles <eles at eles.com> wrote:
>>>>>>>
>>>>>>>
>> "-fno-diagnostics-color
>> Use color in diagnostics. WHEN is ‘never’, ‘always’, or ‘auto’. The
default is ‘never’ if GCC_COLORS environment variable isn't present in the
environment, and ‘auto’ otherwise. ‘auto’ means to use color only when the
standard error is a terminal. The forms -fdiagnostics-color and
-fno-diagnostics-color are aliases for -fdiagnostics-color=always and
-fdiagnostics-color=never, respectively."
>>
>> http://gcc.gnu.org/onlinedocs/gcc/Language-Independent-Options.html
>>
>> It seems to work the same way.
>
>
> Wowo, it *really* works if i set up the GCC_COLORS
>

Doesn't surprise me.  A lot of gcc features work without front end
interaction.  :)

Regards
-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/d.gnu/attachments/20131002/9a98d33c/attachment.html>