cswl

As I see the problem is we install the nightly as `nvm install node` . I can think of workaround to is to first parse `index.json` and instead calling `nvm...

Alright.. I will work on this tonight.. and rebase the PR

One issue I noticed is that, `nvm ls-remote` shows human -readable output... so if you have the latest nightly currently active it shows -> v10.0.0-nightly20171126bb4462681c So I need to handle...

@lukechilds I felt copying the functions from `nvm` was easier.. than handling different cases for `ls-remote`. Tested and working.

@lukechilds I've used `nvm ls-remote` and pattern matching version.. However, I'm getting this error when I have already installed the latest nightly.. ``` Latest nightly: v10.0.0-nightly201711274ca4db0d4c. grep: Unmatched [ or...

You have to manually clear the alias if you once used the older hack. ``` nvm ls v4.8.6 v6.12.0 v8.9.1 -> v9.2.0 v10.0.0-nightly201711274ca4db0d4c default -> stable (-> v9.2.0) nightly ->...

@lukechilds I stopped messing with nightly node... so I didnt notice this yet... I can write our own nightly/rc installer which parses the stuff.. which uses absolute versions and doesnt...

So I took a look at why it's parsing nightly versions as iojs... ``` +nvm_ls_remote_index_tab:91> VERSIONS='' +nvm_ls_remote_index_tab:104> [ -z '' ']' +nvm_ls_remote_index_tab:105> nvm_echo N/A +nvm_echo:1> printf '%s\n' N/A +nvm_ls_remote_index_tab:3> [...

Is this also related? ``` . [cswl:/distros] 1 % proot -v 10 -R jessie proot info: binding = /distros/jessie proot info: binding = /home/cswl proot info: binding = /run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket proot...

Any updates on this? I had to use a workaround mentioned in someon'es dotfiles to fix this