Skip to content
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

NVM install a ~dir in the current working dir rather than the user's home dir #771

Closed
chrisamoore opened this issue Jun 25, 2015 · 8 comments
Labels
needs followup We need some info or action from whoever filed this issue/PR.

Comments

@chrisamoore
Copy link

here is where it installs:
screen shot 2015-06-25 at 6 59 52 am

here are the env vars I have played with:
screen shot 2015-06-25 at 7 00 58 am

I have tried reinstalling nvm to no avail, also this is a fresh install of el capitan on OSX.

@ljharb
Copy link
Member

ljharb commented Jun 25, 2015

NVM_DIR needs to be a directory, not containing nvm.sh - I usually use export NVM_DIR="$HOME/.nvm" or ~/.nvm.

This looks like a problem with the installation script, not directly with your NVM_DIR. Which command did you use to install nvm?

@ljharb ljharb changed the title NVM install a ~dir in the current woking dir rather than the users home dir. NVM install a ~dir in the current working dir rather than the user's home dir Jun 25, 2015
@ljharb ljharb added the needs followup We need some info or action from whoever filed this issue/PR. label Jun 25, 2015
@chrisamoore
Copy link
Author

I used the curl script, I used the one I phased out before to fix this at one point... I will try again tonight. I will respond with my findings TY for the quick response.

@ljharb
Copy link
Member

ljharb commented Jun 25, 2015

Great - please make sure you're using the one from the README, which has the latest version number.

Feel free to delete the literal "~" folder in your home directory too, you shouldn't need that :-)

@chrisamoore
Copy link
Author

rm -rf ~ is bad rm -rf ./~ is much better 😆

Here is another one... it appears that nvm alias default iojs does not set the default node for my terminal... any ideas?

@ljharb
Copy link
Member

ljharb commented Jun 26, 2015

@chrisamoore wait, one thing at a time :-) did installing the latest nvm fix the problem where it creates a literal ~ directory?

@chrisamoore
Copy link
Author

Indeed it did. Thank you for that !!

@ljharb
Copy link
Member

ljharb commented Jun 26, 2015

phew, glad to hear it :-)

I'm closing this, but let's figure out your other issue and decide if we need to file a new one for it. After you run nvm alias default iojs, what does nvm ls output? Note that you still have to nvm install iojs first, before that will have an effect.

@ljharb ljharb closed this as completed Jun 26, 2015
@chrisamoore
Copy link
Author

when I get back to this mac I will open the other issue. TY.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs followup We need some info or action from whoever filed this issue/PR.
Projects
None yet
Development

No branches or pull requests

2 participants