Explicitly Enable Colored Output in Cargo Command Execution #1140
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR ensures that the CARGO_TERM_COLOR environment variable is set to always when invoking the cargo command via the execute_cargo_request function. This change forces cargo to output colored terminal output, enhancing readability and user experience, regardless of the terminal's auto-detection.
Specifically, the following change was made:
Added envs.insert("CARGO_TERM_COLOR".to_owned(), "always".to_owned()); to the execute_cargo_request function to explicitly set the environment variable.
This change improves the consistency of the output and ensures that users receive colored output when running cargo commands through this API.