github/pyenv
1
0
Fork 0
mirror of https://github.com/pyenv/pyenv.git synced 2025-05-02 00:19:10 +00:00
Code Issues Projects Releases Packages Wiki Activity

Improve disabling instruction

Browse source 
Though this is a minor change, I think it is good to have it. It is better to commend a line in config files to disable something than to remove it.
This commit is contained in:
Mostafa Ahangarha 2022-12-16 17:49:24 +03:30 • committed by GitHub
parent 593f820a7d
commit 7509eafdd0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -299,7 +299,7 @@ You can run `rbenv init -` for yourself to inspect the generated script.
The simplicity of rbenv makes it easy to temporarily disable it, or The simplicity of rbenv makes it easy to temporarily disable it, or
uninstall from the system. uninstall from the system.
1. To **disable** rbenv managing your Ruby versions, simply remove the `rbenv init` line from your shell startup configuration. This will remove rbenv shims directory from PATH, and future invocations like `ruby` will execute the system Ruby version, bypassing rbenv completely. 1. To **disable** rbenv managing your Ruby versions, simply comment or remove the `rbenv init` line from your shell startup configuration. This will remove rbenv shims directory from PATH, and future invocations like `ruby` will execute the system Ruby version, bypassing rbenv completely.
While disabled, `rbenv` will still be accessible on the command line, but your Ruby apps won't be affected by version switching. While disabled, `rbenv` will still be accessible on the command line, but your Ruby apps won't be affected by version switching.