Misleading output when a ruby string specifies a nonexistent gemset. #2664

Closed
richardkmichael opened this Issue Feb 28, 2014 · 0 comments

Comments

Projects
None yet
2 participants
@richardkmichael
Contributor

richardkmichael commented Feb 28, 2014

RVM should output:

Ruby ruby-1.9.3-p545 does not have a gemset named 'does-not-exist'.

But instead incorrectly tells me the Ruby version is not installed.

(localhost) ~ rvm list

rvm rubies

=* ruby-1.9.3-p448 [ x86_64 ]
   ruby-1.9.3-p545 [ x86_64 ]


(localhost) ~ rvm ruby-1.9.3-p545 do rvm gemset list

gemsets for ruby-1.9.3-p545 (found in /Users/testuser/.rvm/gems/ruby-1.9.3-p545)
=> (default)
   global
   exists

(localhost) ~ rvm ruby-1.9.3-p545 do true

(localhost) ~ rvm ruby-1.9.3-p545@exists do true

(localhost) ~ rvm ruby-1.9.3-p545@does-not-exist do true
Ruby ruby-1.9.3-p545 is not installed.

@mpapis mpapis added this to the rvm 1.25 milestone Mar 1, 2014

@mpapis mpapis closed this in 5186b32 Mar 1, 2014

mpapis added a commit to rvm/rvm-test that referenced this issue Mar 1, 2014

mpapis added a commit that referenced this issue Mar 1, 2014

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