-
Notifications
You must be signed in to change notification settings - Fork 35
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
sudo apt-vim init installed everything in /root #39
Comments
Good catch. I should be able to quite easily determine which user is is calling |
@caseydentinger In thinking about this further, I'm wondering what the best solution is. It's possible that someone would want to install as root; I don't feel I should stop someone from doing so. Would love to get your input! |
@egalpin what if you did this in the heredoc instead of using the module HOME = "${HOME}" I might be missing something... On Tue, Jun 28, 2016 at 8:14 AM, egalpin notifications@github.com wrote:
|
I think the root of this problem is actually a mistake (my mistake) in the manual installation doc. I've updated it here to reflect the fact that Would you care to give it a whirl? I can run it in a VM, but would love to know if this fixes the specific issue you're seeing |
What about setting PATH to include ~/.vimpkg/bin? Would that eliminate On Tue, Jun 28, 2016 at 8:56 AM, egalpin notifications@github.com wrote:
|
I like this idea a lot. Any time you can install software without super user privileges, it's a win. Just spinning up a VM to test out some changes. Thanks for the feedback |
@caseydentinger Please see #40 :-) The only use of |
Much nicer! Glad I could help! |
Thanks a bunch for your input, closing this issue off :-) |
I do not have always_set_home in sudoers so I think it might be a problem with the script. I am on Debian Stretch and Python 2.7.11+
The text was updated successfully, but these errors were encountered: