mirror of
https://github.com/pyenv/pyenv.git
synced 2024-11-21 20:47:00 -05:00
e2173df4aa
Too many of our users have a shell initialization set up that
inadvertently duplicates some or most of the entries in their PATH,
bringing the system paths again in front of rbenv's shims. If this was a
nested shell (a typical scenario when starting up tmux), `rbenv init`
would get eval'd again but this time, shims won't get added to the front
of the PATH and would only stay and the end of the path, effectively
rendering them useless.
I tried to argue that this is a user problem rather than rbenv's, but I
can't fix everybody shell init when they report bugs. Instead, let's
revert to simpler times in rbenv where we just roll along with the
duplication and don't ask any questions.
This reverts commit
|
||
|---|---|---|
| .. | ||
| rbenv | ||
| rbenv---version | ||
| rbenv-commands | ||
| rbenv-completions | ||
| rbenv-exec | ||
| rbenv-global | ||
| rbenv-help | ||
| rbenv-hooks | ||
| rbenv-init | ||
| rbenv-local | ||
| rbenv-prefix | ||
| rbenv-realpath.dylib | ||
| rbenv-rehash | ||
| rbenv-root | ||
| rbenv-sh-rehash | ||
| rbenv-sh-shell | ||
| rbenv-shims | ||
| rbenv-version | ||
| rbenv-version-file | ||
| rbenv-version-file-read | ||
| rbenv-version-file-write | ||
| rbenv-version-name | ||
| rbenv-version-origin | ||
| rbenv-versions | ||
| rbenv-whence | ||
| rbenv-which | ||