-
Notifications
You must be signed in to change notification settings - Fork 79
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
Serverless plugin not added to autocomplete when installed #96
Comments
The autocomplete command must be run after each plugin install, plugin update, or CLI update. I don’t think this is captured in the docs. |
I did mention that I tried re-running the autocomplete command after installing the plugin. If it helps you can find me on Twilio slack "ghockin". |
Also, on zsh you need to open a new tab or terminal. Try this for bash. |
Thanks for the suggestion, I closed my terminal and no joy. I don't think reloading the bash_profile will help as the command is not being added to the |
Ack. I usually use zsh so haven’t played around much with the bash autocomplete. I’ll try to recreate when I’m at the desk. |
I totally understand it's a busy time this week :D - please hit me up on Slack if you want me to screen share or anything. |
The command Run this command after each plugin install/uninstall/update and CLI update in order to get the most up-to-date auto-complete values. |
Issue Summary
When installing the
twilio-labs\plugin-serverless
installs the plugin correctly except it does not get added to my bash autocomplete. Checking the file at~/.twilio-cli/autocomplete/functions/bash/twilio.bash
does not show theserverless
commands added.All other autocompletion works, including the
twilio-labs/plugin-watch
plugin.Steps to Reproduce
On a Mac using bash:
twilio autocomplete
command outpit slightly as I usebash_profile
:printf "$(twilio autocomplete:script bash)" >> ~/.bash_profile
source ~/.bash_profile
twilio plugins:install @twilio-labs/plugin-serverless
I also tried repeating steps 1 and 2 after installing the plugin but it did not fix the problem
Technical details:
The text was updated successfully, but these errors were encountered: