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
Fixed a bug where --silent mode was failing for nvm use I ran a test
that just ran ```nvm use node --silent``` that I wrote by myself.
Unfortunately I noticed a bug where it still prints out some messages in
different cases. This pull request is to fix that bug. * Added in an argument
called ***quiet*** to the nvm_rc_version() function at *line 339* * Printed
anything inside the nvm_rc_version() only in the scenario where quiet mode is
off * Ran the nvm_rc_version() function in quiet mode only if silent mode is
on in the "use" command of nvm at *line 2990* * Ran *nvm_echo* and *nvm_err*
inside the "use" command of nvm only in the scenario where silent mode is off
(There were 4 scenarios where this was forgotten) * Edited the ```nvm
deactivate``` command to include a silent mode * Changed the help page to
include the --silent option for ```nvm deactivate``` * Added in aliases for
the --silent flag in ```nvm deactivate``` and ```nvm use``` * Used silent
mode inside the ```nvm use``` when running ```nvm deactivate``` inside it and
silent mode is on A test was attached in the 'test/slow/nvm use' directory.
It is named *Running "nvm use node --silent" doesn't print anything*. It runs
```nvm use node --silent and checks``` and succeeds if the OUTPUT matches the
EXPECTED_OUTPUT which is *null* or *''*. When the test was run locally, it
still ouputed results if someone deleted some contents of the *.nvm/* folder.
This output was given from the ```nvm deactivate command```. This was the
reason that the ```nvm deactivate``` was edited to include silent mode.
Also fix `nvm uninstall v1.0.3` so it won't uninstall it if it's the current version.
node versions will still take priority if there's ever a version overlap.
