-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
write_help / write_long_help do not respect Command color settings #3480
Comments
write_help
/ write_long_help
do not respect Command color settings
write_help
/ write_long_help
do not respect Command color settings
This is expected because we |
Okay, but I set In general it would be nice for an application to be able to render colored help to something other than Some ideas:
|
I had been thinking about this and this is one that I don't think we should do. For example, in my applications, I do not rely on clap auto-determining whether color should be shown but instead rely on the
Over time, we do plan to expose |
Cool, thanks. Having the direct control would solve this issue. Not quite clear on why you think having |
When I specify the If I were to call |
I get that for your use case respecting Always would break things, but it seems like you're relying on inconsistent behavior. Sure, it could be that But I also know breaking existing things is not always an option, which was why I suggested |
Please complete the following tasks
Rust Version
rustc 1.58.1 (db9d1b20b 2022-01-20)
Clap Version
3.1.0
Minimal reproducible code
Steps to reproduce the bug with the above code
Just run it and see that the first prints color, but the second does not
Actual Behaviour
No color, even though Color.Always is set
Expected Behaviour
Should print color
Additional Context
No response
Debug Output
No response
The text was updated successfully, but these errors were encountered: