Making upgrades via mise more seamless

[jinnatar]

• When fnox is updated by mise, the old binary is nuked. This causes an activated shell hook to be mad at you because the binary it relies on is gone. (The problem isn't unique to fnox and is definitely annoying with other tools as well, but that's a bigger fish to fry.)
• My instinct to recover was to run fnox deactivate and source fnox activate again, but you can't because deactivate isn't built-in to the function and instead calls the nonexistent binary to generate the commands to deactivate.
• The way to recover the situation manually is to unset -f fnox and re-source. Alternatively, close your session and lose state, which can be annoying if fetching the secrets back requires, say, logging back in to your secrets backend.

This is a conflation of multiple behaviors but results in an annoying situation that I believe could be made better by two changes:

1. Take mise-isms into account and in the fnox function call the binary from ~/.local/share/mise/installs/fnox/latest/fnox instead of hardcoding the path of the binary to the version that was present at the time of sourcing activate.
2. baking in the deactivate logic into the fnox function so it works without the binary present. (Also helps if you actually uninstalled fnox before deactivation.)

[deevus]

Been hitting this exact issue as well. After mise upgrade:

_fnox_hook:2: no such file or directory: /Users/sh/.local/share/mise/installs/fnox/1.5.2/fnox

$ which fnox
fnox () {
	local command
	command="${1:-}"
	if [ "$#" = 0 ]
	then
		/Users/sh/.local/share/mise/installs/fnox/1.5.2/fnox
		return
	fi
	shift
	case "$command" in
		(deactivate | shell) eval "$(/Users/sh/.local/share/mise/installs/fnox/1.5.2/fnox "$command" "$@")" ;;
		(*) /Users/sh/.local/share/mise/installs/fnox/1.5.2/fnox "$command" "$@" ;;
	esac
}
_fnox_hook:2: no such file or directory: /Users/sh/.local/share/mise/installs/fnox/1.5.2/fnox

[davidolrik]

If you eval it with the "latest" path, then that path will be baked into the function

Like so:

eval "$(~/.local/share/mise/installs/fnox/latest/fnox activate zsh)"

[jinnatar]

That would make sense if it worked, but for me it doesn't. It feels like there's a readlink somewhere in there that flattens out all symlinks. Even my home directory symlink is stripped out. (legible username symlink to user uuid.) So even if I source /home/[email protected]/.local/share/mise/installs/fnox/latest/fnox what is harcoded into the function is /home/2fda2a74-xxxx-yyyy-zzzz/.local/share/mise/installs/fnox/1.7.0/fnox