-
Notifications
You must be signed in to change notification settings - Fork 905
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
logging - better default colors #1131
Comments
Yeah, that looks pretty bad. |
@ferventcoder I don't think completely disabling colored output is much of a solution to this, as color has a place in output; drawing attention to errors for example. I don't have much experience with Powershell, most of my experience is with bash where you can declare a foreground color while leaving the BG color alone. Is that not possible in PS? It seems to be a plausible solution for anyone short of those using a light-background color scheme, in which case a flag of something like |
This is still not fixed... very annoying |
@viszu @Zer0t3ch you can simply define your own see the comment above at #1131 (comment) |
@ferventcoder Yes, I saw that, but that doesn't seem to be anything more than a workaround. A consistent deviation in appearance from the default environment (we're not even talking about customized color schemes or anything, although that is where the issue becomes most significant) should not require manual intervention for every single end-user who wants to utilize colored output. If one day GitHub changes their CSS in a way that accidentally makes all usernames invisible, it would stand to reason that people should report that as a problem. (despite the fact that each individual end-user could override the CSS locally or just not pay attention to usernames) I'm well aware that I'm a nobody, and in both the hypothetical and here: y'all are welcome to ignore me. I just figured I'd contribute my 2¢ |
@Zer0t3ch fair statements - perhaps there is something we can do a better job of doing (or be at least a bit more dynamic based on the environment).
I'm going to ignore this statement as you are taking time to provide feedback, which helps improve the product - that sets you above quite a few (thousand/hundred thousand) folks. |
Let's unmark as duplicate and see if we can adjust defaults a bit |
In 0.10.12, this will be released - it will inspect the background color being used and make decisions on whether to put a black background behind the text for INFO, WARN, and ERROR level messages. Appreciate the patience, this should definitely be a good addition. |
For INFO important messages that use Green, do not override the background color unless that color conflicts with visibility. For regular INFO logs, use the same colors already configured in the console.
For warning messages, remove the background color unless that color conflicts with visibility of the text.
For error messages, remove the background color unless that color conflicts with the visibility of the text.
* stable: (chocolateyGH-1131) logging: better defaults for ERROR (chocolateyGH-1131) logging: better defaults for WARN (chocolateyGH-1131) logging: better defaults for INFO (chocolateyGH-1665) sign init.ps1 file (doc) More info on license next steps (chocolateyGH-1503) Warn on incorrectly named license file (chocolateyGH-1292) add note on manifest caching
I didn't grab screenshots while I was going through this unfortunately. |
What You Are Seeing?
The output background is not configurable and overrides the system settings. When the background is set to white the text becomes unreadable.
What is Expected?
Output should not override background settings.
How Did You Get This To Happen? (Steps to Reproduce)
choco config list
arbitrarily.choco config list --verbse --debug
choco config list
Current colors set for the shell
Windows powershell properties.
Output Log
The text was updated successfully, but these errors were encountered: