Activate shouldn't touch HOME variable

[stevvooe]

This really messes with editor and other settings.

[matin]

+50. I use virtualenv in python religiously, and I'm working on a Ruby client. For now, I keep the following in my ~/.profile, which mirror workon from virtualenvwrapper:

function rbworkon () {
    home=${HOME};
    source ~/.sandbox/${1}/bin/activate_sandbox;
    export HOME=${home};
}

[jhermann]

It's not a problem for deployment use with a dedicated user, but for personal use it's a KO criterion. Especially since that also likely means you cannot use specific bang-paths for "run under" behaviour like with virtualenv.

[jhermann]

Also, the README should explain why this is ‘better’ than RVM gem sets, or rbenv.