-
Notifications
You must be signed in to change notification settings - Fork 27
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
Initial commit for zsh native completion support #7
Conversation
@camfrout could you include proposed README updates (if any) for installation process if taking this route? i'd love to test this out but i'm not super familiar with completion functionality in zsh and don't want to accidentally bork up my dotfiles making guesses 😅 |
Sure, I have just added instructions. The easy way is if you are already using oh-my-zsh. |
Co-authored-by: grant <hej@grantwinship.com>
Awesome, thank you! I've got it up and running, so far working very nicely! I'll put it through its paces on client work tomorrow - thanks again this is very cool 🌻 |
i've had zero issues with this @jtcohen6 -- functions flawlessly, install was a breeze: 👍🏻 👍🏻 from me to merge |
Thanks for testing @grantwinship! @camfrout Tiny thing: could you rename the file from |
Hi. I don't think I can, it is actually part of the naming convention for ZSH completion scripts. Source: "Completion functions for commands are stored in files with names beginning with an underscore _, and these files should be placed in a directory listed in the $fpath variable. You can add a directory to $fpath by adding a line like this to your ~/.zshrc file:" Looking at this repo of ZSH completion scripts, we can see that all the scripts are named |
TIL! Thanks for the links @camfrout. I'm good with merging this as-is, then :) |
Add support for native zsh completion for the dbt command
As mentioned in issue #6:
Pros:
Cons: