You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In scop/bash-completion#905, we've added fallback 3rd party completion loaders for various known commands, including some cobra powered ones, and more are expected to be added later. However, as it stands, this mechanism does not have any way for users to specify --no-descriptions if that's their preference.
We could create a bash-completion specific way to accomplish this, but in my opinion this would be better placed in cobra proper. An environment variable would serve this nicely I think: something like COBRA_COMPLETION_NO_DESCRIPTIONS(=non-empty-value) could be equivalent as if --no-descriptions was passed in the generator command line.
The text was updated successfully, but these errors were encountered:
In scop/bash-completion#905, we've added fallback 3rd party completion loaders for various known commands, including some cobra powered ones, and more are expected to be added later. However, as it stands, this mechanism does not have any way for users to specify
--no-descriptions
if that's their preference.We could create a bash-completion specific way to accomplish this, but in my opinion this would be better placed in cobra proper. An environment variable would serve this nicely I think: something like
COBRA_COMPLETION_NO_DESCRIPTIONS(=non-empty-value)
could be equivalent as if--no-descriptions
was passed in the generator command line.The text was updated successfully, but these errors were encountered: