New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$PATH on OS X again #927
Comments
Oh, I just saw the old issue is still open, too: #417 |
bash does not actually throw away the PATH it inherits. Instead it just keeps accumulating more junk onto it. |
to prepend it to $PATH instead of appending it (#950)
Is this intended behavior? I find it quite confusing. E.g. when I'm in another shell (bash, ZSH, or whatever), or even any other tool, where there is already If this is intended behavior, could we have at least an option to disable this? |
@faho Thanks. But it doesn't answer my question: How to disable that? I don't want that Fish changes/reorders my |
You don't. It's something we probably should change. But we shouldn't change it by introducing some weird option, but by making the default better. |
Ah, yes, that would be even better. :) I was thinking that you actually want to keep that behavior, because you (or some other people) think this is the better behavior for some reason. |
So, fish does
/etc/paths
now, which is great. There is one thing that does not work that well though:With system-bash, my path looks like this:
this is pretty much what i expected according to my
/etc/paths
and/etc/paths.d/*
.The problem is, that fish does not reorder things that are in $PATH already when
/usr/local/share/fish/config.fish
is executed. I put aecho $PATH
at the top of the file, and it seems that this:is the path fish inherits from
launchd
.I think that, if a
/etc/paths
file is found, fish should throw away the old path, and rebuild it completely from the files.This would also mean moving the reconstruction of
fish_user_path
after the Mac OS X bit.It also seems fish orders the files in
/etc/paths.d/
a bit differently thanpath_helper
, but I don't think thats really an issue. The files I have in that directory are named as follows:The text was updated successfully, but these errors were encountered: