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

Configure colors of both stdout/stderr #2739

Merged
merged 1 commit into from
May 24, 2016

Conversation

alexcrichton
Copy link
Member

Previously color configuration only affected stdout, not stder as well.

Closes #2734

Previously color configuration only affected stdout, not stder as well.

Closes rust-lang#2734
@rust-highfive
Copy link

r? @wycats

(rust_highfive has picked a reviewer for you, use r? to override)

@alexcrichton
Copy link
Member Author

@bors: r+

@bors
Copy link
Contributor

bors commented May 24, 2016

📌 Commit 45b896e has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented May 24, 2016

⌛ Testing commit 45b896e with merge 3ff108a...

bors added a commit that referenced this pull request May 24, 2016
Configure colors of both stdout/stderr

Previously color configuration only affected stdout, not stder as well.

Closes #2734
@bors
Copy link
Contributor

bors commented May 24, 2016

@bors bors merged commit 45b896e into rust-lang:master May 24, 2016
@birkenfeld
Copy link
Contributor

Nice, thanks!

(I assume it's not considered Cargo's job to forward this setting to rustc?)

@alexcrichton alexcrichton deleted the configure-colors branch May 25, 2016 05:21
@alexcrichton
Copy link
Member Author

For the compiler specifically Cargo could probably recognize --color configure and pass it down, but for other executables like test harnesses it probably wouldn't be able to. Feel free to open an issue for that!

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.

5 participants