-
Notifications
You must be signed in to change notification settings - Fork 511
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
Add an init subcommand #8
Comments
I actually really like this idea. It's something that the "competing" pazi does and would alleviate the concern re: the fish script ("Creating a separate folder with a name like functions in the repository can be confusing." #4 (comment)). Without thinking too deeply, I can't see many downsides to this approach (there are probably more than I'm thinking of, however). The upside is that there is no need for a plugin manager, because the user only needs to add one eval to their config, and everything is then on pace with the binary itself. Overall, I'm a fan. |
I agree, this is a great idea! I will work on this today. |
I hope this can be implemented without hard coding the default aliases of |
I think the best way to do this is to check for environment variables, like |
I've added an |
I've added a command line flag in 34ab8f3. I felt a flag would be better than an environment variable here since it only affects this particular command and not the entire program. |
Would be great to have an init method. This would allow us to source
$(eval zoxide init zsh)
and stay up to date if you make a script change in the future.The text was updated successfully, but these errors were encountered: