mise deactivate doesn't unset what it says it does

[henrebotha]

mise deactivate mentions unsetting MISE_SHELL, __MISE_DIFF, and __MISE_SESSION. Yet all of those retain values afterwards.

2025-03-17 18:05:32 ⋔ ~
» mise deactivate
export PATH='<redacted>'
precmd_functions=( ${precmd_functions:#_mise_hook} )
chpwd_functions=( ${chpwd_functions:#_mise_hook} )
unset -f _mise_hook
unset -f mise
unset MISE_SHELL
unset __MISE_DIFF
unset __MISE_SESSION
2025-03-17 18:05:35 ⋔ ~
» echo $MISE_SHELL \\n$__MISE_DIFF \\n$__MISE_SESSION
zsh
<redacted but non-empty>
<redacted but non-empty>

I'm running in Zsh 5.9.

mise doctor output

version: 2025.3.3 macos-arm64 (2025-03-14)
activated: yes
shims_on_path: no
build_info:

Target: aarch64-apple-darwin

Features: DEFAULT, NATIVE_TLS, OPENSSL, SELF_UPDATE

Built: Fri, 14 Mar 2025 17:34:16 +0000

Rust Version: rustc 1.85.0 (4d91de4e4 2025-02-17)

Profile: release
shell:

/bin/zsh

zsh 5.9 (arm64-apple-darwin24.0)
dirs:

cache: ~/.cache/mise

config: ~/.config/mise

data: ~/.local/share/mise

shims: ~/.local/share/mise/shims

state: ~/.local/state/mise
config_files:

~/.config/mise/config.toml
ignored_config_files: (none)
backends:

aqua

asdf

cargo

core

dotnet

gem

go

npm

pipx

spm

ubi

vfox
plugins:
toolset:

aqua:junegunn/[email protected]

aqua:rs/[email protected]  (missing)

aqua:sharkdp/[email protected]

aqua:sigstore/[email protected]

cargo:[email protected]

core:[email protected]

core:[email protected]

core:[email protected]

core:[email protected]

pipx:[email protected]

ubi:slsa-framework/[email protected]
path:

~/.local/share/mise/installs/node/22.13.0/bin

~/.local/share/mise/installs/python/3.13.1/bin

~/.local/share/mise/installs/pipx-rich-cli/1.8.0/bin

~/.local/share/mise/installs/ruby/3.4.1/bin

~/.cargo/bin

~/.local/share/mise/installs/fd/10.2.0/fd-v10.2.0-aarch64-apple-darwin

~/.local/share/mise/installs/fzf/0.60.2

~/.local/share/mise/installs/cosign/2.4.3

~/.local/share/mise/installs/slsa-verifier/2.7.0

~/.local/share/mise/installs/cargo-xan/0.46.2/bin

~/.docker/bin

~/.local/bin

~/.docker/bin

~/.local/bin

~/.docker/bin

~/.local/bin

~/.docker/bin

~/.local/bin

~/.docker/bin

~/.local/bin

~/.docker/bin

~/.local/bin

~/.docker/bin

~/.local/bin

~/.docker/bin

~/.local/bin

~/.config/zsh/.zcomet/repos/olets/zsh-abbr/bin

/opt/homebrew/bin

/opt/homebrew/sbin

/usr/local/bin

/System/Cryptexes/App/usr/bin

/usr/bin

/bin

/usr/sbin

/sbin

/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin

/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin

/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin

/Applications/Privileges.app/Contents/MacOS

/usr/local/munki

~/Applications/iTerm.app/Contents/Resources/utilities

/home/hbotha/.fzf/bin
env_vars:

MISE_SHELL=zsh
settings:

experimental  true ~/.config/mise/config.toml
No problems found

[henrebotha]

I don't think you can unset an env variable from inside a script. unset MISE_SHELL __MISE_DIFF __MISE_SESSION finally convinces mise doctor that it's deactivated, but only if run from the command line directly.

[henrebotha]

Might be a problem with my shell config. It looks like Tmux was somehow causing this?