-
-
Notifications
You must be signed in to change notification settings - Fork 229
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 more values passed to --color(s) #2410
Comments
No. |
comparing with other linux tools: (checked random dev utilities and https://wiki.archlinux.org/title/Color_output_in_console) Users of auto, always, never:
Simple flags:
Boolean values:
Other:
Just with development tools they look pretty even, but most GNU and linux utilities seem to use the auto, always, never scheme. Additionally looking at the other tools, it seems sometimes unclear what even simple booleans mean (does on mean always or auto?) and in any way it's unclear if omitting values means So I think it makes sense if we switch to that as well (can keep on and off supported for backwards compatibility) because it looks like |
Also improves error message output for unsupported --color values.
Rust's default build tool,
cargo
allows the following values passed to--color
. I find those namings a bit more natural. Shall we support those as aliases aswell?
The text was updated successfully, but these errors were encountered: