Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You will no longer have to do that when you change into a project directory. RVM 1.8.1 had this reenabled by default. (I've added documentation regarding that to the site and to rvm notes)</p> <p>However, since this is an in-directory rvmrc change, and the change in the .rvmrc is not picked up, you can force it by doing an 'rvm reload'. The change <em>should</em> be picked up, but if its not then do the reload.</p> <p>Please post any issues you have after doing this to <a href="https://github.com/wayneeseguin/rvm/issues" rel="nofollow">https://github.com/wayneeseguin/rvm/issues</a></p> <p>Thank you,</p> <p>Deryl R. Doucette</p> <p><b>NOTE:</b> After talking with Wayne, he passed on to me via IRC that he would recommend that you do something along the lines of this in your .bash_profile to aid in what you want:</p> <pre><code> git() { command git "$@" ; [[ -s .rvmrc ]] &amp;&amp; . .rvmrc ; } </code></pre> <p>Also, so you understand, RVM does not run as a daemon in any way shape or form. So what you want RVM to do most definintely will <b>not</b> be added to RVM. As Wayne said, that would be a fun way to mess with someone's head though! :)</p> <p>Think of it this way. While admittedly contrived, the action is still the same. What if someone changes the rvmrc under you while you're in the middle of something (another dev working on the dir and doesn't know you are), or some rogue beastie has hacked your system and changes your rvmrc on you thinking he might gain some additional privs somehow by doing so. (This could be in a group controlled project directory where he's obtained access through another user's account, figures out that you are in the same group, changes the rvmrc underneath you to a different ruby+gemset that he's managed to set up through group permissions of the RVM group in a multi-user install, and causes some arbitrary command to be executed. Imagine further, that you <b>are</b> in, say, the wheel group and you just finished executing some command for root and the timeout has not completed yet for authorization reduction. Since an rvmrc is really nothing more than a bash script, thats not a far stretch of the imagination. So in the end, that makes for a VERY hazardous environment, not to mention an extremely difficult situation to monitor and control.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload