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.

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

Support for FORCE_COLOR #155

Open
cardil opened this issue Jan 26, 2022 · 6 comments
Open

Support for FORCE_COLOR #155

cardil opened this issue Jan 26, 2022 · 6 comments

Comments

@cardil
Copy link

cardil commented Jan 26, 2022

It would be a good idea to apart from supporting NO_COLOR to support easy forcing of color output.

The FORCE_COLOR environmental variable is less spread across industry, but still is used in a couple of libraries, i.e. https://github.com/chalk/chalk#supportscolor

@pellared

This comment was marked as outdated.

donatj added a commit to methodci/checkstyle that referenced this issue Feb 10, 2023
If fatih/color#155 is ever accepted, this will no longer be nessessary
@juanzolotoochin
Copy link

For anyone else who finds this issue, I'm using this workaround:

import "github.com/fatih/color"

func ForceColor() {
	color.NoColor = false
}

Then I just call this at the top of main()

@pellared
Copy link
Contributor

FORCE_COLOR becomes a standard: https://force-color.org/

@pellared
Copy link
Contributor

pellared commented Dec 14, 2023

I think it may be worth to resurrect #156

@cloudyparts
Copy link

FORCE_COLOR option is needed for CI jobs. Gitlab CI supports colorized output in job logs. CI Jobs TERM is set to "dumb" which mutes colors in this package.

@cardil
Copy link
Author

cardil commented Sep 3, 2024

@fatih Would you reconsider your opinion, as https://force-color.org becoming a standard?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants