Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The job of the
rbenv-version-file
command is to print the filepath for the file which sets the current Ruby version. It searches for a.ruby-version
file, traversing upward if such a file is not found until it reaches the root directory.RBENV_DIR
..ruby-version
file is found, it searches again in the current directory (provided thatRBENV_DIR
is different from the current directory)..ruby-version
file, it prints the path to RBENV's global version file ("${RBENV_ROOT}/version"
).This global version file may not actually exist, for example in the following cases:
rbenv global <version_number>
.rbenv local <version_number>
or by manually creating a.ruby-version
file.In the case where the filepath returned by
rbenv-version-file
doesn't actually exist, the result might be confusion on the user's part. This PR attempts to address that confusion, by updating the output ofrbenv help version-file
to specify that this command's output is the filepath which would set the Ruby version, if it exists.