mise
mise copied to clipboard
dev tools, env vars, task runner
At the moment, `mise hook-env` does not respect `settings.ignored_config_paths`, so it is impossible to prevent mise from automatically running this command in a shell in which mise is activated. This...
**Describe the bug** The docs say that we should be able to fetch values of env vars by key, using `mise set `. In version 11.0 I could do this....
[deb-get](https://github.com/wimpysworld/deb-get) provides `apt-get` functionality for .debs published in 3rd party repositories or via direct download. According to [their README](https://github.com/wimpysworld/deb-get?tab=readme-ov-file#adding-software) and [CONTRIBUTING](https://github.com/wimpysworld/deb-get/blob/main/01-main/CONTRIBUTING.md) it seems like the mise deb repository should be...
**Describe the bug** When one already has a virtualenv active, a `.mise.toml` file with a `_.python.venv` directive will add the commanded venv to PATH but always after the already active...
Shebang in `run=` has no effect, but using it in example creates impression it will work: https://github.com/jdx/mise/blob/36a19f87b80aafb15f33dd818f3a4b4a0277c295/docs/tasks/toml-tasks.md?plain=1#L33-L36 _Originally posted by @powerman in https://github.com/jdx/mise/issues/2873#issuecomment-2453996738_
**Describe the bug** ``` mise use -g clang mise ERROR Failed to install [email protected] mise ERROR runtime error: attempt to yield across metamethod/C-call boundary stack traceback: [C]: in ?...
**Describe the bug** mise failed to activate in Nushell 0.99.0: **To Reproduce** 1. Install nushell 0.99.0 2. Add to ~/.config/nushell/env.nu ``` let mise_path = $nu.default-config-dir | path join scripts mise.gen.nu...
Hi, would it be possible to add `json` output for more commands? - `mise doctor --json` (this would allow one to extract `settings`, `dirs`, `warnings`, ...) - `mise env --json`...
**Describe the bug** This is clearly a shell "activate" mode issue. Maybe it's even not a bug, but an UX issue. Maybe it's good enough to just document it instead...
I enjoy the "status.show_tools" setting, but I'd prefer it to not show globally installed tools. An additional option to toggle showing global tools would be nice, possibly make the options...