-
Notifications
You must be signed in to change notification settings - Fork 937
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
tab completion for plugin commands #1116
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/143412259 The labels on this github issue will be updated when the story is started. |
The CLI uses the Goflags library for command argument parsing. It provides the bash command completion for us. |
OK - I understand - and move back to a generated list with keyword is probably not an option. |
There is also the problem that we can't "inject" such a list into what Goflags generates when |
Closing as we have no plans to work on this. Feel free to share any solution that works for you with others in the CF community. |
Hy
it seems tab completion for plugin commands is not working. Hope this can be fixed / added ?
Thanks for looking into this - Michael
Some details:
It seems that cf-cli is generating its own "tab completion"-wordlist when
GO_FLAGS_COMPLETION
is set. (from /usr/local/etc/bash_completion.d/cf-cli:)COMPREPLY=($(GO_FLAGS_COMPLETION=1 ${COMP_WORDS[0]} "${args[@]}"))
cf-cli itself knows about installed plugin commands (see cf -h -a)
However if run with
GO_FLAGS_COMPLETION
e.g.:GO_FLAGS_COMPLETION=1 cf s
The plugin commands are missing. So also (bash) tab completion can't work for plugins.
I'm running on the release:
cf version 6.26.0+9c9a261fd.2017-04-06
The text was updated successfully, but these errors were encountered: