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
Fix Fish shell assignments on array env variables #2169
Conversation
* Correctly handle the case of the variable being unset - This fixes the "missing manpages" bug. * Do not put quotes around array expansions: set -gx PATH $PATH "/blah" # Good set -gx PATH "$PATH" "/blah" # Bad * Add logic for CDPATH, for future-proofing - It is the only other special array variable we have to potentially worry about.
Hmm, just noticed that there are also assignments on "/src/client/opamConfigCommand.ml". Dunno what would be the best way to proceed without duplicating a lot of code. |
* Use "source" instead of "." * Handle CDPATH in `opam config env`
I couldn't fully understand why there is separate logic for generating the shell scripts that go on If this difference between the two functions is not a problem then I think this set of patches should fix #2165 |
Great, thanks! |
This also seems like a 1.2.3 point fix candidate? |
Fix Fish shell assignments on array env variables
I'd like to support @avsm's suggestion to make a point release. This breaks the configuration of fish shells when installing the latest release, 1.2.2 (released a year ago, so I'm assuming this is what most package managers have). |
when is this being merged? @avsm ? |
It's included in the forthcoming opam 2.0 release, which has just been tagged as rc1 |
set -gx PATH $PATH "/blah" # Good
set -gx PATH "$PATH" "/blah" # Bad
to potentially worry about.