add option to force 256 colors (disable truecolor)#156
Open
chaseleif wants to merge 1 commit into
Open
Conversation
Author
|
or, the prep colors could just default to 256 and return if the -t flag wasn't given or, the new option could set a colors max |
This file contains hidden or 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
1 participant
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.
I've had this problem with GNU screen and decided to look at it today and found issue #117. You can work around it by unsetting COLORTERM before running lolcat (then possibly resetting it), the workaround does work for me but is inconvenient.
For a fix, we need to add an option to disable the automatic preference for truecolor.
This does the fix for me, I just use the new --rgbcolor flag.
May close #147 and likely will close both issues #117 and #152.