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
Here's the long version of the story:
I needed to install ruby 2.2.3 (which failed due to some OpenSSL error).
I noticed rvm's warning message that I should update rvm. (I believe the version I was using was 1.29.7, but I'm not 100% sure on that)
So, after failed ruby installation, I gave up on that, but also ran rvm remove 2.2.3 to make any cleanups.
Then I updated rvm with rvm get stable.
This is where rvm became really slow.
EDIT: I just tried rvm get 1.29.7 but didn't help.
If I comment-out source $HOME/.rvm/scripts/rvm in my ~/.zshrc, the shell becomes interactive in about 0.5s. With the line not-commented-out, it jumps to ~2s.
I also tried:
rvm cleanup all rvm reset - this one actually made it faster, apart from when inside of projects with Gemfile (or I'd guess .ruby-version or similar)
What can I do to give you more info you might need so we can debug this further?
rvm get master
Description
Here's the long version of the story:
I needed to install ruby 2.2.3 (which failed due to some OpenSSL error).
I noticed rvm's warning message that I should update rvm. (I believe the version I was using was 1.29.7, but I'm not 100% sure on that)
So, after failed ruby installation, I gave up on that, but also ran
rvm remove 2.2.3
to make any cleanups.Then I updated rvm with
rvm get stable
.This is where rvm became really slow.
EDIT: I just tried
rvm get 1.29.7
but didn't help.If I comment-out
source $HOME/.rvm/scripts/rvm
in my~/.zshrc
, the shell becomes interactive in about 0.5s. With the line not-commented-out, it jumps to ~2s.I also tried:
rvm cleanup all
rvm reset
- this one actually made it faster, apart from when inside of projects withGemfile
(or I'd guess.ruby-version
or similar)What can I do to give you more info you might need so we can debug this further?
Environment info
The text was updated successfully, but these errors were encountered: