Closed czottmann closed 3 years ago
@carlo
Thank you for opening the issue! I'll investigate the cause of the bug 👍
@carlo I'm sorry for the late reply. I created frum referencing to rbenv, so frum does not support version aliases like rvm.
Oh, alright. Well, not a problem, thanks for getting back to me!
Issue description
I've symlinked Ruby minor versions in
$FRUM_DIR/aliases/
, e.g.3.0 → 3.0.2
. Unfortunately, when using the aliases in a.ruby-version
file, they don't seem to do anything, and frum reverts to the global version.My
FRUM_DIR
is set to~/.cache/frum/
.Steps to reproduce the issue
.ruby-version
version file containing an alias version.What's the expected result?
When changing into
alias-test/
, frum resolves the alias2.7
found in the.ruby-version
file to2.7.4
and sets Ruby 2.7.4.What's the actual result?
When changing into
alias-test/
, frum doesn't resolve the alias2.7
and instead falls back to my globally set Ruby 3.0.2.Screenshot:
Note the Ruby version in the last prompt.