From 7509eafdd0ce28a1f01231b6f61acd82125bd2f4 Mon Sep 17 00:00:00 2001 From: Mostafa Ahangarha Date: Fri, 16 Dec 2022 17:49:24 +0330 Subject: [PATCH] Improve disabling instruction 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. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e4e9b3cc..07be9ed9 100644 --- a/README.md +++ b/README.md @@ -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 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.