utils-code/pyenv.pyenv
1
0
Fork 0
mirror of https://github.com/pyenv/pyenv.git synced 2026-09-10 15:46:17 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
830 commits 3 branches 245 tags 15 MiB
Commit graph

8 commits

Author SHA1 Message Date
Victor Lim 9daf81f16e Fix https://github.com/rbenv/rbenv/issues/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.
 2018-02-26 16:49:37 +08:00
Jason Karns 565798d617 Test IFS handling in version-name/version-origin hooks 2016-01-04 09:14:28 -05:00
Jason Karns 0f7a2cad8d Use create_hook helper 
Use extracted create_hook helper in tests for:

- exec
- hooks
- rehash
- version-name
- version-origin
- which
 2016-01-04 09:14:25 -05:00
Jason Karns f880dc6d6f Remove support for legacy version file 2015-12-28 21:34:07 -05:00
Mislav Marohnić 6e30032278 Simplify version-name, version-origin hook tests 
No need for helper function that's gonna be used just once.
 2015-12-23 17:39:14 +01:00
Mislav Marohnić 4fde4ecbaf Ensure RBENV_VERSION_ORIGIN is not inherited from environment 
It's only supposed to be set from `version-origin` hooks, but not
inherited from environment in case it was set.
 2015-12-23 17:26:53 +01:00
Jason Karns c3a5f91ed0 create hook: version-origin 
Expose a `version-origin` hook.

It is invoked *before* the traditional `rbenv-version-file` lookup. Because `version-origin` is traditionally run immediately after `version-name`, then any plugin hooks that alter `version-name` would have done so. Thus, running `version-origin` prior to printing the origin gives those plugins a chance to alter the `version-origin` to match.

If any of the hooks set `$RBENV_VERSION_ORIGIN`, then it is used as the return value. Otherwise, the existing logic continues to return "environment variable" or "filename" as appropriate.

This change, in conjunction with the `version-name` hook, makes a clean seam by which plugins can inject their own ruby version setting logic. Using this seam, as opposed to altering `$RBENV_COMMAND_PATH` from the `which` hook, means that the version name and origin are set more reliably and so `version`, `version-name`, `version-origin` and `which` all work as expected. Indeed, even PS1 works now.
 2015-12-23 17:22:31 +01:00
Mislav Marohnić ab197ef51e add tests for version commands 2013-04-08 23:16:35 +02:00