You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original chruby command allows specifying "fuzzy" ruby versions without the patch number, e.g. 2.4 which will load the highest matching available version from the 2.4 series.
Unfortunately, chruby.el does not understand this, and can actually mismatch if there's another version of ruby available which contains the "fuzzy" substring. Concretely, if you have 2.2.4 and 2.4.1 installed, calling chruby-use-corresponding when .ruby-version contains 2.4 will activate 2.2.4, not 2.4.1.
I'm a totally elisp newbie, but I think the fix will be on this line:
The original
chruby
command allows specifying "fuzzy" ruby versions without the patch number, e.g.2.4
which will load the highest matching available version from the2.4
series.Unfortunately, chruby.el does not understand this, and can actually mismatch if there's another version of ruby available which contains the "fuzzy" substring. Concretely, if you have
2.2.4
and2.4.1
installed, callingchruby-use-corresponding
when.ruby-version
contains2.4
will activate2.2.4
, not2.4.1
.I'm a totally elisp newbie, but I think the fix will be on this line:
chruby.el/chruby.el
Line 82 in 3eddd2f
The text was updated successfully, but these errors were encountered: