pyenv

442 커밋

2 브랜치

237 MiB

트리: bf39d88d11

커밋 그래프

작성자 SHA1 메시지 날짜

작성자	SHA1	메시지	날짜
Mislav Marohnić	e2173df4aa	Revert "Don't duplicate shims in PATH" 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 `03fa148e81`. Fixes #369	11 년 전

Mislav Marohnić

e2173df4aa

Revert "Don't duplicate shims in PATH"

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 03fa148e81.

Fixes #369

11 년 전

1 커밋 (bf39d88d11ef341d0be5a845f170699bd40678c2)