Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[REQUEST] Implement CLICOLORS / support CLICOLOR_FORCE #3028

Closed
abesto opened this issue Jul 7, 2023 · 3 comments
Closed

[REQUEST] Implement CLICOLORS / support CLICOLOR_FORCE #3028

abesto opened this issue Jul 7, 2023 · 3 comments
Labels
Needs triage

Comments

@abesto
Copy link
Contributor

abesto commented Jul 7, 2023

How would you improve Rich?

According to the documentation, rich currently supports NO_COLOR and FORCE_COLOR. https://bixense.com/clicolors/ seems to be gaining a fair amount of traction, and specifies CLICOLOR_FORCE. It'd be nice if Rich respected this env var as well.

What problem does it solve for you?

In a polyglot environment, this would allow me to more confidently write just CLICOLOR_FORCE=1 instead of FORCE_COLOR=1 CLICOLOR_FORCE=1.
@github-actions
Copy link

github-actions bot commented Jul 7, 2023

Thank you for your issue. Give us a little time to review it.

PS. You might want to check the FAQ if you haven't done so already.

This is an automated reply, generated by FAQtory

@willmcgugan
Copy link
Collaborator

Rich will try to support standards, but I’m not convinced this is enough of a standard yet.

@github-actions
Copy link

I hope we solved your problem.

If you like using Rich, you might also enjoy Textual

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@abesto @willmcgugan