wayneeseguin/rvm — Issue #722: settings files and project "scripts" should not be named the same thing
Author: niedfelj
Created: 2012-01-25 01:18:49+00:00
State: open

should reconsider the naming convention of .rvmrc for $HOME/.rvmrc and project specific .rvmrc files. I ran into an issue today that wasted half a day because of this:

I recently installed an SSD in my macbook and moved my old drive to be storage, symlinking in dirs that I wanted from the old drive under my new home dir:

/Users/joel/Documents -> /Volumes/Macintosh HD/Users/joel/Documents

rvm would when cding into that dir, preserve the default ruby, HOWEVER, when Terminal would restore or I would open a new tab in that symlinked dir, rvm would fail because there was still a .rvmrc in my old /Volumes/Macintosh HD/User/joel folder and instead of seeing it's current working dir as now under /Users/joel/Documents it would see it as /Volumes/Macintosh HD/Users/joel/Documents. And, because that is not my home dir, it would see the /Volumes/Macintosh HD/User/joel/.rvmrc and think it was a PROJECT .rvmrc instead of the old settings file that I forgot was there. Better namespacing could prevent this kind of thing from happening, and it seems like when you are going to have .rvmrc project files that filter all the way up without any kind of warning you need this.