From 63c471d0204f0b06cca640c3a49037e4f914b63f Mon Sep 17 00:00:00 2001
From: fsc-eriker <72394365+fsc-eriker@users.noreply.github.com>
Date: Mon, 30 Oct 2023 21:10:26 +0200
Subject: [PATCH] Describe --no-rehash option in the manpage (#2832)

(Closes: #2831)
---
 man/man1/pyenv.1 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/man/man1/pyenv.1 b/man/man1/pyenv.1
index 0629e894..c3d2de1b 100644
--- a/man/man1/pyenv.1
+++ b/man/man1/pyenv.1
@@ -234,6 +234,7 @@ Skip this section unless you must know what every line in your shell profile is
 \fBSets up your shims path\.\fR This is the only requirement for pyenv to function properly\. You can do this by hand by prepending \fB$(pyenv root)/shims\fR to your \fB$PATH\fR\.
 .IP "2." 4
 \fBRehashes shims\.\fR From time to time you'll need to rebuild your shim files\. Doing this on init makes sure everything is up to date\. You can always run \fBpyenv rehash\fR manually\.
+You can disable this functionality by adding \fB--no-rehash\fR to the end of your \fBpyenv init\fR command line.
 .IP "3." 4
 \fBInstalls the sh dispatcher\.\fR This bit is also optional, but allows pyenv and plugins to change variables in your current shell, making commands like \fBpyenv shell\fR possible\. The sh dispatcher doesn't do anything crazy like override \fBcd\fR or hack your shell prompt, but if for some reason you need \fBpyenv\fR to be a real script rather than a shell function, you can safely skip it\.
 .IP "" 0