5 ms·

I don't use RVM, and I've got a few excuses: RVM doesn't work with fish. Fish is the biggest innovation in command-line shells in so long, and I'd rather drop

by mhansen 16y ago

I don't use RVM, and I've got a few excuses: RVM doesn't work with fish. Fish is the biggest innovation in command-line shells in so long, and I'd rather drop RVM than drop fish. Also, RVM hijacked my 'cd' command, so that 'cd' wouldn't take me back to my home directory any more. I don't like things messing with workhorse commands that I depend on - 'cd' has to work.

poet 16y ago
'cd' hijacking is definitely a bug. I can't reproduce that behavior. How long ago did that happen? Overall I've found rvm to be very solid software.
- mhansen 16y ago
  Not a bug - it's part of RVM's design. RVM reads .rvmrc files in each directory you change into. How does it do this? By redefining 'cd' to be a function wrapping the real CD command, with some extra RVM stuff in between the changing of directory and return. Check it out: http://github.com/wayneeseguin/rvm/blob/master/scripts/cd http://github.com/wayneeseguin/rvm/blob/master/scripts/cd My problems ('cd' with no arguments didn't take me back to my home directory any more) occurred about a month ago (I was using the fish interop mode - that might have been the problem), and it's probably been fixed since. But the whole thing scared me out of continuing with RVM. If there's a bug in RVM, I sure as hell don't want it to manifest in my 'cd' command. I need to be able to change directory, and my scripts rely on it to always work.