-
Notifications
You must be signed in to change notification settings - Fork 375
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
Coloring should be disabled if output is not a TTY #21
Comments
Good point, let me fix that. |
Could this have an optional flag to force colors? I would like to use glow to preview markdown files in ranger but the colours get stripped. |
@CallumHoward You can explicitly set a style to enforce it: |
Amazing, thanks! |
@muesli can you please re-open this ticket? Thanks. |
Hey everyone. I can look into this one. This is the same issue as #654, right? If so, let’s track it there. |
Yes it seems to be the same issue. The ticket #654 is more recent but that shouldn't be an issue as the current ticket is closed. Thanks for looking into it. |
Awesome, sounds good. Let’s track the issue there, then. |
I also made my ugly hack to force colors Also takes a lot of time to do something, but at least I was able to remove the garbage: script -q -c "glow README.md" | tail -n +2 |
It's sort of opposite the point of this library, but with things like the auto-fetch-from-github functionality users could find themselves doing something like the following:
…which of course would appear littered with ASCII escape codes.
The text was updated successfully, but these errors were encountered: