Readme help, force color output #24
Merged
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
If you use a custom build script and sub-programms don't output color, it could be that they assume the output has no colors. `CLICOLOR_FORCE=1` as environment variable helps.
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.
If you use a custom build script and sub-programms sometimes do not output color. CLICOLOR_FORCE=1` as environment variable helps.
First I thought that SublimeANSI was not working. But it turned out that gnu-make assumed that the output pipe has no color support and so did not output any colors. Fortunately gnu-make supports
CLICOLOR_FORCE.To save the time of other people this information would be a very good nice-to-have in the readme file.