-
Notifications
You must be signed in to change notification settings - Fork 4
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
Don't Install in /usr/share/..
#59
Comments
Thanks for the feedback. Honestly I would have really wanted to choose a user directory, but the thing is that there isn't always one. I tried to check how I could complicate my logic to try and find a user owned directory, and resort to the current situation as a fallback, but since I don't even know which user directory to choose I would have to guess, which may be both unwanted and unpredictable. Another option is to update the The last option that comes to mind is to let the user pass in the path, which is pretty straightforward, but might still prove problematic if the user tries to upgrade and chooses a different directory (resulting in conflicting versions of the completion scripts). I would love to hear your thoughts on these options. |
in such cases you can consider prepare a file and ask to user for source it. Just for an option |
Thank you for the suggestion, and sorry for the late reply. I like your suggestion and can implement it quite easily. By default running the activate script will print out a line to add to |
I've wanted
zsh
completions for pypi ecosystem for a long time, so I want to thank you for getting the ball rolling on this. My strong feeling, however, is that you shouldn't force the installation anywhere superuser privileges are required. Namely,find_completion_script_dir
should prefer a user directory infpath
.Completions for Python itself:
_python
are typically vendor-distributed, and therefore in/usr/share/zsh/functions/Completion/Unix
. At least it's this way in Ubuntu Linux. For now I just trick it by writing a dummy file_python
elsewhere.The text was updated successfully, but these errors were encountered: