You can clone with
HTTPS or Subversion.
After successfully installed a ruby version using ruby-build, chruby does not update the installed ruby list:
$ ruby-build -v 2.0.0-preview2 ~/.rubies/2.0.0-preview2
Installed ruby-2.0.0-preview2 to ~/.rubies/2.0.0-preview2
Currently, my workaround is to reopen a new terminal to see the updated list. Does it happen to anyone else here?
Yes, this is because chruby loads Rubies at startup. I could add a chruby_load function?
Ya, that will be great!
Or is it possible to always reload the list, right before we run chruby to list the installed rubies?
Not currently, since users can explicitly define RUBIES with custom globs.
I see, what chruby_load function that you suggested will do?
Probably just these two lines. chruby_load would then be called at the bottom of the script.
ah good catch. I guess chruby_load should re-set RUBIES.
0.3.3 will initialize RUBIES to () on load. I will probably add a reload.sh or refresh.sh file in 0.4.0 that users can load; since not everyone installs Rubies on the fly.
Expand file globs in RUBIES at runtime
This prevents the user from having to source chruby.sh whenever Ruby
installations are added or removed.
I'm still having this problem.
$ chruby --version
chruby version 0.3.4
I have to run this to get the newly installed ruby recognized by chruby:
source /usr/share/chruby/chruby.sh # archlinux
Sorry for the wait. There will be a chruby_install function in 0.4.0. Until then, simply restart the shell or re-load chruby.sh.