New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support CLICOLOR(_FORCE) to control colored output #1928

Merged
merged 1 commit into from Mar 25, 2017

Conversation

Projects
None yet
2 participants
@jhasse
Copy link
Contributor

jhasse commented Mar 17, 2017

Currently the colored output of Waf can be disabled by the environment variable NOCOLOR. Especially when running Waf inside a CI server (which logs the output), it is required to pass --color=yes. This gets tedious when you have multiple invocations, e. g.

./waf --color=yes configure
./waf --color=yes build
./waf --color=yes test

Therefore an environment variable to force colored output would be handy.

In order not to have too many different env variables one has to remember, I hope that CLICOLOR and CLICOLOR_FORCE can become some kind of standard, see https://bixense.com/clicolors/. CMake also supports CLICOLOR_FORCE, so I think it might be a good fit for Waf, too. Also the ANSI plugin for Sublime already encourages to set CLICOLOR_FORCE=1, so that Waf's output there would now be in color :)

@ita1024 ita1024 merged commit aa73787 into waf-project:master Mar 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment