-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: force colours #33
Comments
It's possible by setting the I'm considering also adding |
Works like a charm! |
Please see PR #38 to add parameters to override the environment variables. |
This would be very useful for me as well – in pytest-logikal I'm running some checks in a (non-interactive) subprocess but I'd still like to have the output be colored when collecting the results. Would there be any chance to merge PR #38 and release it? |
Yes, I'll merge it now and release it in the next day or two, hopefully we can include #44 as well. |
That would be totally awesome! Thank you very much. |
are these options documented somewhere? |
They're not, and they should be. Thanks for the prompt, I'll open an issue to make sure they're added. |
Please see PR #60. |
Hi,
I have a special case where I pipe my script using termcolor to
fzf --ansi
to keep colours. But it seems that_can_do_colour()
wants stdout to be interactive, so this is not possible for now.Would it be possible to init the module with forced colours?
The text was updated successfully, but these errors were encountered: