I'm trying to make a gemset the default whenever I start a new terminal in Mac OS X:
rvm use 1.9.3@rails3.2 --create --default
That seems to work, the rails3.2 gemset becomes the current gemset:
$ rvm gemset list
gemsets for ruby-1.9.3-p0 (found in /Users/me/.rvm/gems/ruby-1.9.3-p0)
global
=> rails3.2
$
But when I open up a new terminal, the rails3.2 gemset is no longer the current:
$ rvm gemset list
gemsets for ruby-1.9.3-p0 (found in /Users/me/.rvm/gems/ruby-1.9.3-p0)
global
rails3.2
$
What do I do?
You can use this command.
or
rvm --default use <ruby version>@<gemset name>
orUse following command to make a gemset as default.
eg.
Interesting that nobody has mentioned rvm alias. Try your version-specific variation of this, works for me:
Have you tried specifying
rvm --default use
after the gemset is created so passing:and then seeing if that sticks? Using create and default at the same time isn't something I've tried before, it's the only thing that strikes me as out of place.
Given the discussion below I'd offer this as a means for dealing with the problem. (Personally, I'd probably implode rvm and start over.) But, if you wanted to try to make a go of it with this install then I'd look at your
.rvm
folder, specifically in.rvm/environments/default
which will contain all the environment variables exported for the default environment. Here you'll findrvm_gemset_name
this may be set incorrectly and isn't updated for some reason (permissions?) or is set correctly in which case its some other environment issue. You could try manually setting it here in the file if its not correct.You can use this command
$ rvm use <ruby version>@<gemset name> --create --ruby-version
For example : ruby version = ruby-2.1.2 gemset name = gem320
It would be
$ rvm use ruby-2.1.2@gem320 --create --ruby-version.
Even if you open other tab also, it will preserve the settings.