Maybe _mise_hook should be called at the end of the activate content? #3260
Closed
AndydeCleyre
started this conversation in
Ideas
Replies: 2 comments
-
I don't recall the reasons but this was the behavior for a while but I removed it because it caused more problems than it solved |
Beta Was this translation helpful? Give feedback.
0 replies
-
It looks like this is happening now, with #3373, right? Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using Zsh, and found that when I replaced otherwise-installed tools with mise-installed tools, such as cargo-installed
eza
with mise-installedubi:eza-community/eza
, the path would not include the relevant folder by the time I check for that tool's presence in later.zshrc
code.For example, if after loading up mise in my
.zshrc
I have:then the second
alias
will be used.I found I could fix this by prefacing that code with:
forcing the PATH to be updated before the check.
Or, since I write the output of
mise activate zsh
to a file and source that, adding_mise_hook
as a final line to that file also works.Would it make sense to include that in the official
mise activate
content, so that tools which ought to be in the PATH regardless of current folder can be made available during shell startup?Beta Was this translation helpful? Give feedback.
All reactions