Using `cd` makes the nvm directory the number-one directory in `autojump`'s database---which is somewhat confusing since the user basically never `cd`s to it directly!---so here's an alternative method that doesn't use the `cd` command. I've checked it works in both Bash and Zsh.
Under certain network environments, due to poor implementation of file
download caches (immoral Chinese ISP), the direct download of Node.js
packages (http://nodejs.org/dist/node-$VERSION.tar.gz) will be
redirected to alternative urls using 302 redirections, which are not
handled by `curl --process-bar` by default. Instead, curl will "fail"
silently without creating any output file or error exitcode.
(Tested under Ubuntu 12.04 Desktop)
Fixed by adding "-L" switches to the curl commands responsible for
downloading the binary and source node.js packages.
The same fix as #207, just for fools like me who have `which` aliased to `type` in OS X. Without this escape, a very cryptic error message is emitted (though the install ultimately succeeds, as long as one actually has `curl` installed).
Fixes issues #232 and #244 where "nvm ls" returns inconsistent results depending on the number of node versions installed. This updated fix uses the find and sort commands only. Tested in bash v3.2.48 and v4.2.25, and zsh v4.3.11.
Fixes issue 232 that occurs in at least bash v4.2.25 where "nvm ls" returns "N/A" no matter how many versions of node have been installed. The fix uses a combination of the find, tr and basename commands instead of basename only. Tested in bash v3.2.48 and v4.2.25 and zsh v4.3.11.
basename doesn't accept options in bash. This causes the VERSIONS variable get the 'N/A' value for $ nvm ls command.
From basename man page:
NAME
basename - strip directory and suffix from filenames
SYNOPSIS
basename NAME [SUFFIX]
basename OPTION
DESCRIPTION
Print NAME with any leading directory components removed. If specified, also remove a trailing SUFFIX.
--help display this help and exit
--version
output version information and exit
coreutils version used in Linux Mint 14 Nadia.
GNU coreutils 8.12.197-032bb September 2011 BASENAME(1)
No idea if this flag exists on FreeBSD or other unixes (if they use gnu coreutils shouldn't be any problem)
Since we run in interactive context the builtin `cd' may have been aliased to
print some additional info when invoked, thus it's safer for us to avoid
parsing the output from subshells which calls it.
For instance in .bash_profile I have the following function to redefine
`cd' such that it will list the destination directory contents:
cd () { builtin cd "$@" && ls -F --color=auto }
line 188, `which shasum > /dev/null 2>&1` will be replaced by:
'/usr/bin/shasum > /dev/null 2>&1'
but, `/usr/bin/shasum` needs filename argument which is ommited and the
test results always 'false'.
Fixes issue #39
ZSH's default globbing behaviour differs from Bash. If there is no
match, ZSH itself will print the error message.
This means that piping a commantd's STDERR to /dev/null will not
hide it.
By unsetting the NOMATCH option we get a behaviour similar to Bash.
Signed-off-by: Tomas Sedovic <tomas@sedovic.cz>
This fixes issue with curl not being installed before nvm is initially sourced
and then curl subsequently being installed.
removed creation of global curl function (after error detected) which
overwrites the system tool, preventing execution of later installed
curl binary
When sourcing nvm.sh, if there are no version of node installed the command
`nvm ls default` silentry fails, however it's return status code (`$?`) is
still set to non-zero, which means an error.
This patch simply avoids this issue by making sure the status code after
sourcing is ok so that people that put the returned status codes in their
command line prompt don't get an error every time `nvm.sh` is sourced.
Now sorts correctly in all instances and prints highlights
even in sorted views. Also will output a list of matching versions
for commands of the form nvm ls 0.4* rather than just printing one
version. nvm version 0.4 still prints the single latest matching
version, however.
Trying to install already installed version causes misleading message
from curl and nvm:
$ nvm install v0.4.11
curl: (33) HTTP server doesn't seem to support byte ranges. Cannot
resume.
nvm: install v0.4.11 failed!
Of course, resuming interrupted installs is still possible (script
checks for existance of `$VERSION` in `$NVM_DIR`, not `$NVM_DIR/src`).
Aliases are stored as plaintext files in the $NVM_DIR/alias dir.
They may store either an explicit version (v0.3.6) or an implied version
("latest"). The latter is a "moving target", and thus possibly
dangerous, but can be useful, too.
Adds a cache of all versions available on nodejs.org using simple empty files as placeholders. When a new version is installed, it will replace the placeholder with a directory.
This makes it easier for users to see what versions are available for install, and what the latest and stable versions are.
00Davo
Martin Iwanowski
Max Zhao
Daniel Stockman
Jeremy Satterfield
Code Whale
Cliffano Subagio
Tim Caswell
Derek Keller
Koen Punt
Donovan James King
Miguel Cobá
Emanuele Aina
jnlin
GPad
Yosiya Hinosawa
A.J
Marsup
Kosei Moriyama
Sebastian Cohnen
hisanori
wlaurance
Joel Wietelmann
Nathan LaFreniere
Bill Caputo
Matthew Metnetsky
rummik
Aravind Ramanathan
fatshotty
Tomas Sedovic
Gerhard Lazu
Wtfcoder
David Hagler
Chakrit Wichian
Lucian Holland
Caio Romão
Jeffrey D. Van Alstine
Maciej Małecki
Lucian Holland
Scott Bronson
Marcelo Diniz
Will
Christopher Roach
Geoffrey Huntley
Evan Meagher
Kieran Huggins
Jakub Nešetřil
Carter Thaxton
Tim Caswell
Isaac Wolkerstorfer
isaacs