Do all ANSI codes get stripped out of help menu when printing to non-terminal/non-tty?

[fritzrehde]

In my after_help macro I am calling a function that returns a string. This string contains some colored ANSI codes. I have not conditionally disabled the colors based on whether or not I am printing to a tty, in my code. However, I still observe that my color ANSI codes seem to be stripped out when calling <app> -h and not printing to a tty e.g. stdout. I am positively suprised by this, but wanted to ask if this is expected behaviour. Are ANSI codes always stripped out of the help menu, including strings generated for after_help, when printing to non-tty?
Thanks!

[epage]

Yes, it is intentional that any API call that accepts StyledStr may have ANSI escape codes put in them and they will automatically be stripped when printing to "unsupported" terminals. For legacy Windows consoles, they will instead be covnerted to wincon API calls.

We wanted to allow users to style their text but had several limitations

• We didn't want to provide a bespoke styling API (it'd end up looking like termcolor which is frustrating to use and doesn't integrate well with other work)
• We didn't want users worrying about whether the string they were giving clap would go to stdout or stderr

This led to the creation of anstream. This means its available for you to use in your application as well. Recently, I switched cargo over to it.

[fritzrehde]

Cool, thanks for the in-depth answer!