Enhance handling of colored output #1418
Merged
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.
Please check if the PR fulfills these requirements
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)Enhances commands output.
Colored output on Windows Powershell and Command Prompt is not handled correctly and output is mangled with escape characters.
Also users have no way of disabling colored output if necessary.
Colored output now works correctly on Windows Powershell and Command Prompt and users can easily disable colored output in different ways:
NO_COLOR
env var (https://no-color.org/)output.no_color
config setting or related env varOUTPUT_NO_COLOR
--no-color
flagtitled accordingly?
Nope.
None.
See how to contribute