[Bug]: PATHの順番が不本意

[Okabe-Junya]

Bug description

（ローカル; M1MBPの）シェルで echo $PATH すると

$ echo $PATH
/Users/junyaokabe/.nvm/versions/node/v18.12.1/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Apple/usr/bin:/Applications/Wireshark.app/Contents/MacOS:/Applications/Postgres.app/Contents/Versions/latest/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/junyaokabe/.pyenv/shims:

のようになる．（一部のみ抜粋）/usr/local/bin とかが先に来てしまっていて，そっちが優先されるので非常にまずい．

How to reproduce

zsh立ち上げて echo $PATH

Expected behavior

/etc/profile によって読み込まれるやつは最後に来てほしい．（/usr/local/bin とか）

Actual behavior

その逆になる

Environment

m1 mbp，arm64上のzsh

Additional context

No response

[Okabe-Junya]

仮想環境系のパスはなんか解決した．

• Bugfix #70

その他はまだ色々問題ありそう．

~  $ echo $PATH  | sed -e 's/:/\n/g' C
/Users/junyaokabe/.pyenv/shims
/Users/junyaokabe/.nodenv/shims
/Users/junyaokabe/.rbenv/shims
/Users/junyaokabe/.nvm/versions/node/v18.12.1/bin
/usr/local/bin
/System/Cryptexes/App/usr/bin
/usr/bin
/bin
/usr/sbin
/sbin
/Library/TeX/texbin
/usr/local/share/dotnet
~/.dotnet/tools
/Library/Apple/usr/bin
/Applications/Wireshark.app/Contents/MacOS
/Applications/Postgres.app/Contents/Versions/latest/bin
/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin
/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin
/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin
/opt/homebrew/bin
/opt/homebrew/sbin
/opt/brew_x86/bin
/opt/brew_x86/sbin
/Users/junyaokabe/go/bin
/Users/junyaokabe/.pyenv/bin
/opt/homebrew/opt/openjdk@11/bin
/opt/homebrew/opt/llvm/bin
/Users/junyaokabe/.rbenv/bin
/opt/homebrew/opt/openssl@3/bin
/Users/junyaokabe/.fig/bin
/Users/junyaokabe/.local/bin
/Users/junyaokabe/.fzf/bin

[github-actions]

Message to comment on stale issues. If none provided, will not mark issues stale