jdx
jdx
These should be scoped, maybe in an "args" object
Hmm, so I do like this idea, however I've had plans which might not be written down and are quite vague but essentially I want to tie usage completions and...
No but I do work around that problem in mise via a mutex. Perhaps that mutex could just go into demand directly? I can’t think of a use-case where you...
not currently, no. It's probably a use-case for tool options.
it's possible #2083 may fix this, I fixed a few things around "latest" versions
I'll let you decide, I don't have a strong preference. I can't think of any problems with that.
actually scratch that, this is expected behavior with `mise x`. `mise i` will use the latest version but `mise x` will use the "latest" version that is currently installed. It...
e.g.: anytime you install something mise creates a symlink like `~/.local/share/mise/dummy/latest` that points to the latest installed version, it has nothing to do with whatever the latest available version is—in...
the purpose here is to avoid unnecessarily fetching runtimes, updating is explicit with commands like `mise install` or `mise upgrade`
I think it is mostly intuitive—otherwise calling a shim would automatically install the latest version every time you call it which would be more strange. This could probably be documented,...