nodenv v1.2.0 Release Notes

Release Date: 2018-12-23 // over 5 years ago

    ๐Ÿ›  Fix fish subcommand completion

    ๐Ÿ’… This allows subcommand style plugins to properly autocomplete.
    Existing commands are not affected.

    ๐Ÿ‘ Example, say you have support for rbenv foo bar --flag, then
    this allows the last --flag argument to be properly completed.

    ๐Ÿ›  Fix pyenv -> rbenv typo

    partly resolve #759

    • some versions of bash (e.g. 4.3.11) complain about clobbering
      /dev/null, use bash's explicit >| operator to ignore noclober
    • not sure if the original #759 report has the same cause

    - rbenv/rbenv#759 (comment)

    Enforce absolute RBENV_DIR

    This prevents CDPATH from becoming an issue.

    Closes #866.

    Don't unset CDPATH

    rbenv-version-file: ensure that the version file is a file

    Forwarded from pyenv/pyenv#606.

    rbenv 1.1.1

    ๐Ÿ›  Fixed rbenv init - output to work w/ no args and bash's set -u.

    Quote directory name in variable assignment

    ๐Ÿ›  Fix some issues reported by shellcheck

    ๐Ÿ‘ Better error message for rbenv shell

    0๏ธโƒฃ Shell integration is not enabled by default. This means that, from all the
    commands from rbenv commands, only "shell" won't work right away.

    Replace "no such command" with a more descriptive message that points to
    rbenv init instead.

    ๐Ÿ›  Fix rbenv/rbenv#1065

    ๐Ÿ’Ž Command rbenv version-name > .ruby-version will create an empty .ruby-version file
    before running rbenv-version-file. This causes rbenv-version-file to return empty
    string which in turn causes rbenv-version-name to return system.

    โ†ช Ensure size of .ruby-version is non-zero as a workaround.

    โœ‚ Remove ableist language

    rbenv-which: change PATH only for the "command -v" lookup

    This is not really necessary, because rbenv-which is used in a subshell
    currently, but makes a difference if rbenv-which would be sourced.

    rbenv-prefix: do not silence rbenv-which for system version

    This suppressed any output when using RBENV_DEBUG=1 and does not really
    hurt to have in the unlikely case that it should fail; you would get
    two error messages now:

    ๐Ÿ’Ž rbenv: ruby: command not found
    rbenv: system version not found in PATH