jdx
jdx
frankly I see this as an antipattern. It means I can't search a codebase to find where the env vars are defined
definitely
do you have experimental enabled? that actually goes down a completely different code path (see #863 if you're curious what) I'm not sure if that's related off the top of...
that's not a bug, `mise up` updates to the latest in the range you've specified. For what you're doing you can just do `mise use --pin yamllint@latest`
that said, there is the downside of that where you don't have `--interactive` and can't upgrade all of them at once. I also suspect you won't be the only user...
I'd be open to a PR for this but I think it will be a bit tricky to write. It will probably need to respect the existing specificity for the...
this is by design. If someone doesn't want to manage a particular tool via mise they don't have to and by default mise won't complain about it. If you want...
It's an area that's been continuously iterated on. At different points in rtx different warnings/behavior/defaults around this have been tried. Finding the right balance to show effective warnings in hook-env...
my hope was that the "not_found" handler that worked in your situation would mitigate this problem. It probably has to some extent but it has a lot of gaps `which...
I don't want to show the warning if the not found handler is in place. That will mean I show them a warning telling them to install manually but chances...