-
Notifications
You must be signed in to change notification settings - Fork 266
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
Remove requirement for $GIT_SUBREPO_ROOT from _git-subrepo zsh completions #183
Comments
@rbellamy regarding your first point:
and completion worked. If I leave out the copy, it doesn't work. Maybe you should check if the path for the completion is correct on your side, and make sure you open a new shell after adding the script. About the issue topic: Why would you want to remove it? |
@perlpunk the assumption made by the completion script is that it has been installed via a git clone, and thus it's important to know where the If you copy the completion script, as-is, directly into
My
Every other completion script in my system, including I recognize that the Or to make my point from another angle, to my mind testing whether a command has been installed correctly from within a completion script is asking it to do more than it should - the presumption is that the command is available on the users path, or completion isn't necessary in the first place. Which brings me to my final argument - why add yet another path variable to the user's environment? |
@rbellamy ok, then that's more a general question about $GIT_SUBREPO_ROOT - currently the docs say it's required to source the .rc file. |
👍 |
…on handler Fixes ingydotnet#183 I don't know how to comprehensively test this, but I have verified that some basic completions work correctly
this was fixed in #476 |
When the
_git-subrepo
completion script is dropped directly into/usr/share/zsh/site-functions
the completions JustDon'tWork(tm).Furthermore, the check doesn't actually DO anything except bark and barf if the variable hasn't been set - the completions work just fine without it.
The text was updated successfully, but these errors were encountered: