3 ms·
I rather liked Fish's zero config approach but I found their handling of the PATH very hard to work with day to day. Perhaps it was just my familiarity with hav
by richeyryan 6y ago
I rather liked Fish's zero config approach but I found their handling of the PATH very hard to work with day to day. Perhaps it was just my familiarity with having a bunch of statements to alter the PATH in a config file but it felt very opaque, I always had to look up how to add stuff to the PATH and I had great trouble trying to remove stuff from the PATH.
- qmmmur 6y agoIt's easy once you understand universal global and local variables.
- mattgreenrocks 6y agoThat is a valid issue. Should be remedied in an upcoming release.
- richeyryan 6y agoOh wow that's great to hear. Do you have any resources I could reference? A Github issue discussing the intended solution or something?
- mattgreenrocks 6y agohttps://github.com/fish-shell/fish-shell/pull/7028 https://github.com/fish-shell/fish-shell/pull/7028
- gpanders 6y agoI LOVE the way fish handles PATH. I just modify the $fish_user_paths variable (which is a universal variable) and I don’t have to modify any config files. E.g. to permanently add `~/.cargo/bin/` to your PATH just do set fish_user_paths $fish_user_paths ~/.cargo/bin once from an interactive shell, and you’re done!