You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
A binstubbed program can't run a binstubbed program as a sub-process within a project directory (with a
Gemfile
).For example,
guard
(which runsrspec
) runs therspec
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:
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
.The text was updated successfully, but these errors were encountered: