with '' will be ignored, and an empty message aborts the commit.
On branch master
Your branch is up to date with 'origin/master'.
Changes to be committed:
new file: .github/__init__.py
new file: .github/workflows/__init__.py
new file: .vscode/__init__.py
new file: __init__.py
new file: test/__init__.py
new file: test/fast/Aliases/__init__.py
new file: test/fast/Aliases/circular/__init__.py
new file: test/fast/Aliases/lts/__init__.py
new file: test/fast/Listing paths/__init__.py
new file: test/fast/Listing versions/__init__.py
new file: test/fast/Set Colors/__init__.py
new file: test/fast/Unit tests/__init__.py
new file: test/fast/Unit tests/mocks/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/inside-n_m-nested-pkg/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/inside-n_m-nested/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/a/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/a/b/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/a/b/c/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-both/a/b/c/d/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/a/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/a/b/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/a/b/c/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-n_m/a/b/c/d/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/a/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/a/b/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/a/b/c/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/nested-pkg/a/b/c/d/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/no-nesting-both/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/no-nesting-n_m/__init__.py
new file: test/fast/Unit tests/mocks/project_dirs/no-nesting-pkg/__init__.py
new file: test/fast/__init__.py
new file: test/install_script/__init__.py
new file: test/installation_iojs/__init__.py
new file: test/installation_node/__init__.py
new file: test/mocks/__init__.py
new file: test/slow/__init__.py
new file: test/slow/nvm exec/__init__.py
new file: test/slow/nvm reinstall-packages/__init__.py
new file: test/slow/nvm reinstall-packages/test-npmlink/__init__.py
new file: test/slow/nvm run/__init__.py
new file: test/slow/nvm uninstall/__init__.py
new file: test/slow/nvm use/__init__.py
new file: test/slow/nvm_get_latest/__init__.py
new file: test/sourcing/__init__.py
new file: test/xenial/__init__.py
Path lists in environmental variables often give special meaning to
empty entries (e.g. in PATH or MANPATH). These are represented by
leading or trailing colons, or by doubled colons in the middle of the
list.
Adjust the awk invocation to correctly deal with trailing colons by
printing the separator before every field except the first, and then
printing the final separator that is read from the input - this will
either be a colon or the null string. This preserves leading and
trailing colons in all cases while not adding extra colons in the wrong
place.
Add test to confirm the correct behaviour.
Fixes#3144
I had to dig into #2410 to learn about the `PROFILE=/dev/null` technique to install without appending to my shell config. Figured this note would be good to add in the main installation docs.
Also added a note on how to do this as a one-liner which was not obvious for me.
the `nvm.sh` file assigns and exports an `NVM_CD_FLAGS` variable if it
was sourced from a zsh shell. the fact that it's exported means that
it'll be assigned in all child processes, including the `nvm-exec`
script, which uses bash as the interpreter.
Bash's `cd` command doesn't have a `-q` flag, so if the `NVM_CD_FLAGS`
is assigned `-q`, the script will error out and incorrectly claim that
the node version isn't installed.
this also manifests itself in the `nvm exec` command.
Example:
```console
$ nvm exec 16.14.0 npm --version
Running node v16.14.0 (npm v8.3.1)
/Users/<ME>/.nvm/nvm.sh: line 28: cd: -q: invalid option
cd: usage: cd [-L|[-P [-e]] [-@]] [dir]
both the tree and the node path are required
N/A: version "v16.14.0 -> N/A" is not yet installed.
You need to run "nvm install v16.14.0" to install it before using it.
```
To address this, we unset the `NVM_CD_FLAGS` at the start of the
`nvm-exec` script, before loading `nvm.sh`.
