-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 is broken #3753
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Looks like we're still waiting on the upstream PR to merge. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Given the state of spf13/cobra#899, should we consider cobra abandoned? Can we pull in a fix without cobra? Or should we plan to move off of it? |
Any updates on it? |
@vkudrik see upstream issue. |
It looks like k3d recently resolved a similar issue. I wonder if we can take whatever approach they did. |
Update: we have updated to cobra 1.0.0 recently (to add fish completion), but that still doesn't have the zsh completion fix. They did fix that in their master branch afterwards but they haven't cut a release including it (last release was in April 🤷♂️ ) |
Duplicate of #3999 |
Bug Report
zsh completion is failing with error:
It is happening because
[$LINKERD_NAMESPACE]
is not escaped.What is the issue?
Unable to use autocompletion for linkerd in zsh
How can it be reproduced?
Install zsh, add completion by running
source <(linkerd completion zsh)
, try autocomple any linkerd commandLogs, error output, etc
None
linkerd check
outputNot related
Environment
Possible solution
There is PR opened in cobra package to fix issue - https://github.com/spf13/cobra/pull/899/files but not yet merged.
Additional context
The text was updated successfully, but these errors were encountered: