-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Zsh Completion Issues #1226
Comments
Hi @dakaneye, Cobra 1.0 does not support The next release of Cobra will add this support which is already part of the master branch. If you have been reading the documentation of the master branch, then your confusion is very understandable. |
Yep that's why I was confused! Thanks for the update |
@dakaneye considering the situation I don't believe there is anything to fix (except maybe making a release 😉). Would you mind closing this issue in this case? |
No problem! Btw, @marckhouzam any estimated time frame in the release? |
I don't know myself. Maybe @jharshman or @jpmcb would know the plan for the next release? |
For clarity, it looks like |
Hi all, reporting 2 issues here:
ValidArgsFunction
.[
or]
, they don't get escaped. This was mentioned in New zsh completion script seems broken #881 (comment) but I don't think it was fixed.If I edit the generated shell completion script to escape that option description square bracket, then completion works, but only partially.
To provide an example, the dynamic completion in my ValidArgsFunction is simply listing the docker image tags on the local system. Once the square brackets are commented out in the generated script, I'm able to get completion to work, but it doesn't call my
ValidArgsFunction
, it just lists the sub commands:I noticed for both Bash and Fish generated completion scripts that there is handling for the dynamic completion, but not in the Zsh generated scripts.
Here's the generated completion script section with the option descriptions:
Note that for output and scope the descriptions contain square brackets that should be escaped.
Also Note that for bash and fish completions, the generated script works out of the box.
The text was updated successfully, but these errors were encountered: