Skip to content

nodenv 1.2.0
Compare
Choose a tag to compare
@jasonkarns jasonkarns released this 23 Dec 18:25
· 198 commits to master since this release
v1.2.0
beec76f

  • 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

    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

Assets 2