mirror of
https://github.com/pyenv/pyenv.git
synced 2024-11-14 20:39:55 -05:00
Update rbenv init
instructions
The README details `eval`ing `rbenv init -`, but for some shells (such as fish) there's a difference in what should be run. It turns out that `rbenv init` on its own will print correct instructions, so we should point users to running that command instead.
This commit is contained in:
parent
d6ab394efd
commit
35ca51fe88
1 changed files with 4 additions and 10 deletions
14
README.md
14
README.md
|
@ -180,13 +180,8 @@ easy to fork and contribute any changes back upstream.
|
|||
|
||||
**Zsh note**: Modify your `~/.zshrc` file instead of `~/.bash_profile`.
|
||||
|
||||
3. Add `rbenv init` to your shell to enable shims and autocompletion.
|
||||
|
||||
~~~ sh
|
||||
$ echo 'eval "$(rbenv init -)"' >> ~/.bash_profile
|
||||
~~~
|
||||
|
||||
_Same as in previous step, use `~/.bashrc` on Ubuntu, or `~/.zshrc` for Zsh._
|
||||
3. Run `~/.rbenv/bin/rbenv init` for shell-specific instructions on how to
|
||||
initialize rbenv to enable shims and autocompletion.
|
||||
|
||||
4. Restart your shell so that PATH changes take effect. (Opening a new
|
||||
terminal tab will usually do it.) Now check if rbenv was set up:
|
||||
|
@ -237,9 +232,8 @@ $ brew update
|
|||
$ brew install rbenv
|
||||
~~~
|
||||
|
||||
Afterwards you'll still need to add `eval "$(rbenv init -)"` to your
|
||||
profile as stated in the caveats. You'll only ever have to do this
|
||||
once.
|
||||
Afterwards you'll still need to run `rbenv init` for instructions
|
||||
as stated in the caveats. You'll only ever have to do this once.
|
||||
|
||||
### How rbenv hooks into your shell
|
||||
|
||||
|
|
Loading…
Reference in a new issue