Closed AndrewVos closed 12 years ago
Yup. Explanation here: https://github.com/hmans/rbfu/issues/11
Ok I agree with not walking up directories above the current directory, but could we at least check for existence of $HOME/.ruby-version? This doesn't seem like it would have much overhead?
That doesn't fix the problem, I'm afraid. What if you move deeper into a project's directory structure (as opposed to outside of it)? You'd have to start traversing the path again, as described in the other issue, in order to make sure you keep using the project's version of Ruby as opposed to the one denoted in $HOME/.ruby-version.
(On a side note, what I do on my system is that whenever I decide I'm "done" working on a specific project, I just jump to my home directory using cd
, where the .ruby-version file is then picked up.)
Ok I definitely see your point now. It would be irritating if you traversed to a subdirectory of a project and rbfu switched back to the default.
On Sun, Jun 10, 2012 at 8:32 PM, Hendrik Mans < reply@reply.github.com
wrote:
(On a side note, what I do on my system is that whenever I decide I'm "done" working on a specific project, I just jump to my home directory using
cd
, where the .ruby-version file is then picked up.)
Reply to this email directly or view it on GitHub: https://github.com/hmans/rbfu/issues/14#issuecomment-6231146
If you're in a directory with a .ruby-version and you cd out of it you would expect rbfu to switch back to whatever is in ~/.ruby-version.
This is not the case.