New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rbenv-exec only allows executables found by rbenv-which #865
Comments
|
I just ran into this issue again. the rbenv-env plugin is intended to print out useful env vars relevant to rbenv (that is, env vars such as This is clearly suboptimal. In reality, the ideal implementation of rbenv-env would simply be Do you have any thoughts on how this should operate? |
When testing the nodenv-env fork of this, I discovered that the rbenv-which command fails when a ruby version isn't set. Since the result of that command is only used when a ruby version is explicitly set, it doesn't make sense to attempt the command in all cases (especially when it fails in the negative case). Related to rbenv/rbenv#865
Related: #187 |
Any updates on this? Would be really nice to attempt to execute as is if no shim exists. |
Allows to execute arbitrary command in the context of selected ruby. rbenv#865
I don't think this is really a bug but more of a feature request. Presently,
rbenv exec
doesn't do what is advertised on the cover. Per the help:To me, this means that
rbenv exec foo
should be the same asPATH="$RBENV_ROOT/versions/1.9.3-p327/bin:$PATH" foo
. But instead, rbenv-exec checks rbenv-which first. So if the provided command doesn't exist under the currently selected ruby, then we get an error rather than simply invoking the command.I'm not sure if this behavior belongs in rbenv-exec (though that's my inclination). But it should be possible to simply execute a command while letting rbenv set up the correct
PATH
for me first.The text was updated successfully, but these errors were encountered: