binstubbed programs can't run binstubbed programs.

[docwhat]

A binstubbed program can't run a binstubbed program as a sub-process within a project directory (with a Gemfile).

For example, guard (which runs rspec) runs the rspec under ${RBENV_ROOT}/versions/<version>/bin not the one in ${RBENV_ROOT}/shims.

This is because after rbenv exec "${program}" runs in the shim, the rbenv puts a bunch of other paths in front.

You can see this by running:

ruby -e "puts ENV['PATH']"

The first paths are the specific ruby version path in ${RBENV_ROOT}/versions, then the ${RBENV_ROOT}/plugins/*/bin directories and then finally comes the ${RBENV_ROOT}/shims directory.

Its an annoying failure only noticeable if you have more than one version of (for example) rspec installed and the wrong one is picked up by running ${RBENV_ROOT}/versions/<version>/bin/rspec.

[ianheggie]

I wonder if adding the binstub directory at the front of the path would work, or if we would get some execution loops? Any thoughts?

[docwhat]

The shims run rbenv exec -- I don't know how that works. If it doesn't use the PATH, then it should work...

EDIT: I said 'binstubs' instead 'shims'.

[ianheggie]

I am no longer using rbenv, so I am happy to receive pull requests with tests to consider, but I am no longer actively developing the plugin.

[ianheggie]

I worked around this problem by swapping to chruby and direnv - Any takers for fixing this in rbenv-binstubs?