Can I remove all default messages?

[will-j-wright]

Hi,

I'm writing an enterprise application which requires localization. Is there some way of removing all the default strings so I can replace them with the dynamically localized version?

For example, the usage message always prints "Usage:" before my usage message, and any unexpected argument prints "error: unexpected argument "something" found". These are always in English, which isn't acceptable for our use case, and I can't find any way of completely disabling them. I have override_help and override_usage set, but "Usage:" is always printed.

I see that there is a localization issue opened (#380), but we already have our own localization solution--all I want to do is disable all default string printing.

[epage]

I see that there is a localization issue opened (#380), but we already have our own localization solution--all I want to do is disable all default string printing.

At the moment, that issue is focused on overriding strings or hiding them and not baking in support for a specific solution.

However, we overlooked mentioning the [default value: ...] string and its now covered:

• Remove hard coded [] messages with Arg::hide_default_value, Arg::hide_possible_values, Arg::hide_env

[epage]

Oops, misread "default strings" as "the default value string". The "current steps" on #380 cover all of that.

[will-j-wright]

Thanks for the solution.

I understand you receive a lot of requests from a lot of people, and this is probably not a common request by any means, but it would definitely be helpful (for our use-case specifically, haha) if there was a simple way of disabling all built in printing and just leaving up to the user what to display in the case of any command error.

We’re in the weird space where we don’t need all the great suggestion/message generation features of clap, but it would be nice to have something a little more straightforward than just using clap_lex.

Anyways, thanks for your help!

[epage]

We already have errors generic over printing, my hope as part of my clap 5 prep / implementation will be to do something similar for help (#2914).