fix: use PATH instead of fish_user_paths + tests #1709
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Update
asdf.fish
to modify$PATH
directly, rather than using$fish_user_paths
. This respects the user's choice between a universal or global$fish_user_paths
, addressing an issue where the previousasdf.fish
made this decision on behalf of the user.Modifying
$PATH
directly was recommended by @faho (long time Fish shell contributor) and avoids assumptions about$fish_user_paths
being global or universal, which should be the shell users decision. Note that in fish$PATH
cannot be a universal variable (it's simply inherited from the parent process), so it does not have this issue.This approach also aligns with initialisation scripts from other projects, such as those from brew and pyenv that also set PATH directly, ensuring simplicity.
A side effect is that this also fixes tests and resolves test interdependencies caused by the persistence of the universal variable across runs.
Fixes: