Mislav Marohnić

> The instructions suggest to do a github checkout. - No problem, I go to corresponding section. Now it suggests to do automatic curl script rather than doing manually. -...

Update: the documentation should now be clearer on many topics including installation, which now has fewer steps, should be easier to follow, and hopefully have less pitfalls for the average...

A command to manage plugins would be interesting but not sure if we would have it in core. I'm not completely sold yet, but others might be. However since this...

@sstephenson: How about an `rbenv-update` command which updates rbenv itself from git and executes `update` hooks from plugins? That way ruby-build could publish a hook that updates itself from git...

@olivierlacan I do believe that this should be easier for the user, and what you're suggesting sounds completely reasonable. However, there's something that feels slightly risky about software that updates...

> I realize saying this out loud how much is involved for this to happen. And I'm a bit exhausted, but does that even still sound like something reasonable @mislav?...

I definitely agree; unfortunately I have no ideas how to approach solving this issue. This requires group thinking /cc @sstephenson @sheerun

@benwoodward and others: If you have a problem with `vagrant` or `heroku` commands, use `rbenv whence` to find which Ruby versions have installed gems for those projects, uninstall those gems...

@royzinn Did you `rbenv rehash` after you uninstalled heroku gem from every version? That should get rid of `/Users/royzinn/.rbenv/shims/heroku`

Symlinking heroku into rbenv/shims/heroku will work for a short while but will get rewritten the next time something runs `rbenv rehash`, so you can't count on it as a permanent...