nvm use *version* not properly switching after install with aptana terminal

[mayorbyrne]

I've been using nvm-windows successfully for a few weeks. For a while I only had 0.10.32 installed. I primarily use Aptana terminal inside eclipse IDE.

node just released 0.10.33 recently, so, using the terminal inside eclipse:

nvm list

showed that I was using 0.10.32 (only version that was installed).

then
nvm install latest

Once it displayed that npm and node had been installed,

$ nvm use 0.10.33
Now using node v0.10.33

I then issued the following commands, and receieved the results:

It might be of note that I was using 0.10.32 fine before this inside the same terminal. Anyways. after that, I opened up the windows command prompt:

Note no asterisk in the nvm list.

After that I went back to eclipse (did NOT restart it), and everything ran fine, as it should.

I do not know if this is a "bug," or if it can be duplicated. Just simply describing my issue.

[coreybutler]

The problem here is that the Aptana terminal is not a true console. It is an emulator, based on Cygwin. It's basically like trying to run NVM for Windows on Linux. Emulation introduces a lot of quirks.

When you run nvm use x.x.x from within Aptana, it is trying to direct the symlink using a Unix path, i.e. /c/path/to/node instead of a Windows path like C:\path\to\node. However; you can use a version in a normal console and it will propagate to Aptana because cygwin is re-reading and converting the PATH variable in realtime.