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

Disable color output when no TTY is present. #481

Merged
merged 1 commit into from
Jul 29, 2014
Merged

Disable color output when no TTY is present. #481

merged 1 commit into from
Jul 29, 2014

Conversation

fnichol
Copy link
Contributor

@fnichol fnichol commented Jul 29, 2014

This should help clean up kitchen output in CI environments, using
the kitchen command with unix pipes, etc.

In other words:

kitchen test | cat

Should not output colors.

Currently, the only catch is that colors are still used inside the
instances for tools such as RSpec. This may require work in the Busser
component.

Closes #330

This should help clean up kitchen output in CI environments, using
the kitchen command with unix pipes, etc.

In other words:

    kitchen test | cat

Should *not* output colors.

Currently, the only catch is that colors are still used inside the
instances for tools such as RSpec. This may require work in the Busser
component.

Closes #330
@sethvargo
Copy link
Contributor

👍

@fnichol
Copy link
Contributor Author

fnichol commented Jul 29, 2014

@sethvargo the frustration ends today 😄

fnichol added a commit that referenced this pull request Jul 29, 2014
Disable color output when no TTY is present.
@fnichol fnichol merged commit 4fbc491 into master Jul 29, 2014
@fnichol fnichol deleted the tty-color branch July 29, 2014 21:17
@test-kitchen test-kitchen locked and limited conversation to collaborators Nov 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No way to disable colors
2 participants