Mislav Marohnić

`rbenv-exec` was solely designed for powering the shims mechanism, and for that purpose it makes sense to focus only on executables that are in ruby bin directory. However I see...

Hi, thanks for the contribution. I'm having some concerns that this is perhaps over-engineered. In which cases would this help? Also, why would we ever allow `rbenv rehash` to run...

Thank you so much for developing this solution. The code looks great, but I'm afraid I won't pull this into rbenv because I'm trying to reduce the amount of functional...

> So it seems that from the very introduction of `RBENV_DIR`, it wasn't respected consistently by rbenv's subcommands. Excellent sleuthing. Yes, `RBENV_DIR` consistency wasn't great historically, but you have to...

Well to close the gap, I have no objections to having `rbenv-local` respect RBENV_DIR when reading. Although, I still think it should _write_ exclusively to PWD.

I thank you for your prior in-depth research on this, but I have given this another thought and I am not so much in favor of making this change. It...

Thank you for the implementation, explanation, and the ensuing discussion, but I remained unconvinced that this is a change I want in rbenv, and in the interest of keeping rbenv...

Your problem is that, when calling your script from `ruby`, you have already gone through rbenv to reach the ruby. So, PATH is already set up. However from ruby you're...

It's a common pitfall. You can clear the current env from a Ruby process like so: ``` rb rbenv_root = `rbenv root 2>/dev/null`.chomp unless rbenv_root.empty? re = /^#{Regexp.escape rbenv_root}\/(versions|plugins|libexec)\b/ paths...

True. I also don't think the above workaround is what users should be doing in the long run. However, that is what they need to do with the current version...