Skip to content
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

force color use when MOCHA_COLORS is set to 'always' #965

Closed
wants to merge 1 commit into from

Conversation

jaredly
Copy link

@jaredly jaredly commented Aug 30, 2013

useful for an env that doesn't want to forkpty but still wants colored output.

@travisjeffery
Copy link
Contributor

env var likes this typically just check for any value for them to be on. e.g. MOCHA_COLORS=1 mocha test. and afaik, the process global object shouldn't need to be guarded.

travisjeffery added a commit that referenced this pull request Sep 22, 2013
@jaredly
Copy link
Author

jaredly commented Sep 22, 2013

Sweet. I was borrowing from npm's pattern but it's no big thing. Thanks for
getting that in!

https://github.com/isaacs/npm/blob/5a94bd86ac1d1b530d95d9dc1a2299941f4ca761/lib/npm.js#L290

On Sat, Sep 21, 2013 at 9:30 PM, Travis Jeffery notifications@github.comwrote:

env var likes this typically just check for any value for them to be on.
e.g. MOCHA_COLORS=1 mocha test. and afaik, the process global object
shouldn't need to be guarded.


Reply to this email directly or view it on GitHubhttps://github.com//pull/965#issuecomment-24875423
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants