Detect true-color terminal support for pygmentize #2160
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
jeanas
requested changes
Jun 12, 2022
|
I added a second commit, which documents how the terminal determines the maximum number of colors supported. |
jeanas
approved these changes
Jun 13, 2022
|
Thanks! |
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.
For the
pygmentizecommand line, this pull request adds detection of true-color support on the terminal and makes that the default formatter. It looks up theCOLORTERMenvironment variable having a value oftruecoloror24bit. If that is the case, it sets the default formatter to use theTerminalTrueColorFormatter.The
COLORTERMenvironment variable is a convention that has been adopted by some terminals for specifying true-color is supported.