rvmrc switching breaks `rvm list` output #737

batter opened this Issue Jan 31, 2012 · 4 comments


None yet

3 participants

batter commented Jan 31, 2012

Just upgraded to rvm 1.10.2. There is a new feature where when you execute an rvm list it has various identifiers for the different ruby status's. For example:

$ rvm list

=* ree-1.8.7-2011.03 [ i686 ]
   ruby-1.9.2-p290 [ x86_64 ]
   ruby-1.9.3-p0 [ x86_64 ]

# => - current
# =* - current && default
#  * - default

This is nice, however when you switch to a project that has an .rvmrc file which requires switching to a ruby other than what you have specified to be rvm's default ruby, the list identifier for the current ruby (=>) doesn't appear next to the list to indicate that it is the currently selected ruby.

Here is the gist for a DTF file where the last test is failing, an example of the bug.


What is going on with RVM? Its pretty much in an unusable state right now.

batter commented Jan 31, 2012

@nacengineer This is the latest repository source. It says on the website that you have the option of installing the latest repository source version or the most stable version. I choose to use the head with the understanding that I will have access to the newest features but that I may encounter more bugs. If you are concerned about stability then you should use rvm get stable instead of rvm get head.

Besides, this is more of a cosmetic issue than anything and I'm sure it will be fixed in the next release.


yeah I figured that out after a bit thanks to this article.


Although even the stable version has an issue with the pointer to the current version being used. But it is stable enough. However I'm a little disappointed as RVM stable was always so stable in the past. Guess I'll stop panicking and get back to work.

Thanks for the heads up!

@mpapis mpapis was assigned Feb 1, 2012
@mpapis mpapis closed this in 9595238 Feb 1, 2012
mpapis commented Feb 1, 2012

@fullbridge-batkins thank you for finding and writing test

@nacengineer please report all issues, any test cases are also welcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment