This repository has been archived by the owner on Jun 1, 2024. It is now read-only.
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.
While trying to figure out which "expose mise binaries" approach is best for my
~/.huskyrc
file I noticed that in your What doesmise activate
do? FAQ, that the shims approach is preferable over themise hook-env
approach.But in another FAQ mise isn't working when calling from tmux or another shell initialization script this is not mentioned and
mise hook-env
is suggested as the fix.This PR updates the "mise isn't working when calling from tmux or another shell initialization script" FAQ to iron out this inconsistency, by mentioning the "add shims to path manually" approach since I think that is the recommended approach over
mise hook-env
(I assume it's faster too).bit more info jdx/mise#734