-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Make a symbolic link to directory of current version of node #734
Comments
Nope, this doesn't make any sense for IDEs simply can't work well with it unless they can invoke a shell session and source |
No, I'm not suggesting changing the basic mechanism of nvm. I'm suggesting adding the symbolic link, not setting $PATH to it. |
This sounds like |
Maybe I'm just too lazy to type more commands every time I use nvm to change versions 😄 |
Having a global symlink makes sense, but tying it to |
Feature request.
Is it possible to make a symbolic link to directory of current version of node?
For example, ~/.nvm/current --> ~/.nvm/versions/node/0.12.2/. It's really useful for OSX users using GUI applications.
nvm works perfect under command line. But it's difficult to setup environment variables for GUI applications under OSX. Before Yosemite, we can use /etc/launchd.conf. In Yosemite, we have to use a more complicated method (see Stack Overflow).
In both methods, it requires a reboot or restart of GUI application to for EV's changes to take effect.
nvm now changes $PATH when changing versions of node. The changes won't take effect for GUI applications.
My solution now is:
I created a symbolic link to the directory of current version of node, like ~/.nvm/current. Then I add Users/XXX/.nvm/current/bin to $PATH for GUI applications. When changing versions, I changes the symbolic link. So the version change will take effect immediately for GUI applications.
Here's a example.
![image](https://cloud.githubusercontent.com/assets/910023/7218577/216f75be-e6aa-11e4-9757-51d5e8e34155.png)
IMHO, it also makes $PATH looks nicer.
The text was updated successfully, but these errors were encountered: