Re: [riot-devel] Colorized compiler output not for Emacs users

2017-08-08 Thread Hauke Petersen

Hi Kees,

I was not aware of the compatibility issues for Emacs users when 
enabling the colored gcc output. So yes, I'd say a conditional flag 
preventing this on demand is indeed needed. I just opened a PR with that 
fix [1].


Cheers,
Hauke

P.S. AFAIK many in the community actually use VIM for coding. Personally 
I use sublime-text for most editing...


[1] https://github.com/RIOT-OS/RIOT/pull/7451


On 06.08.2017 19:00, Kees Bakker wrote:

Hey,

Since commit 2811adc0 we get colorized gcc output.
Hmm. That's unfortunate for Emacs users (I'm probably one of
the very few).
Emacs parses the compiler output and now it cannot match the error
messages anymore.

Would it be possible to add some variable to disable the coloring? 
(There's

more than just this GCC diagnostics-color.) Something like DONOT_COLOR.
This would be in the same category as QUIET, I guess.

But really, I'm curious what people use to develop RIOT-OS. VIM?, 
Eclipse? Atom?

Emacs?


___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


[riot-devel] Colorized compiler output not for Emacs users

2017-08-08 Thread Kees Bakker

Hey,

Since commit 2811adc0 we get colorized gcc output.
Hmm. That's unfortunate for Emacs users (I'm probably one of
the very few).
Emacs parses the compiler output and now it cannot match the error
messages anymore.

Would it be possible to add some variable to disable the coloring? (There's
more than just this GCC diagnostics-color.) Something like DONOT_COLOR.
This would be in the same category as QUIET, I guess.

But really, I'm curious what people use to develop RIOT-OS. VIM?, 
Eclipse? Atom?

Emacs?
--
Kees
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel