jdx
jdx
`mise rm`
right now `mise rm|remove` is an alias for `mise uninstall`, however I am wondering if that should stay the case. I am considering whether it should have slightly different behavior...
@pepicrft mentioned he might be getting to a point where .mise.toml configs are getting large and could be split into separate files. I suspect this may be due to tasks....
similar to #1447, it should be possible to execute arbitrary scripts which "export" env vars like this: ```toml [env] _.run = "./myscript" ``` Where unlike in #1447, this would be...
### Provide environment information ```bash N/A ``` ### To Reproduce ``` $ asdf list all vault 0.1.0 0.1.1 0.1.2 0.2.0 0.3.0 0.3.1 0.4.0 0.4.1 0.5.0 0.5.1 0.5.2 0.5.3 0.6.0 0.6.1...
the user might be using a shell like fish that won't work with this script
if a single task is running with no dependencies, there is no need to show the `[PREFIX]` thing in the output I don't think.
I think it would be nice if you could add tasks in a dedicated file like `tasks.toml`. This could be configured in `.mise.toml` probably like this: ```toml tasks = {import...
I'd like a global option for specifying `MISE_ENV`, e.g.: `mise run --env=staging test`.
I'd like to see a companion service for mise to generate and serve precompiled binaries for a set of environments. This would be similar to Homebrew's bottles. Because plugins already...