How to access MISE_PROJECT_DIR or equivalent information within hook which runs in the current shell (shell is set to zsh)?

[AndydeCleyre]

The docs say that hooks are run with MISE_PROJECT_DIR set, but that doesn't seem to be the case for shell hooks. Is there a way to figure out what folder the config file is in (the project root) within a shell hook?

$ cat mise.local.toml

[hooks.enter]
shell = "zsh"
script = "typeset -p MISE_PROJECT_DIR"

$ cd ..
$ cd -
(eval):typeset:8: no such variable: MISE_PROJECT_DIR

[jdx]

but that doesn't seem to be the case for shell hooks

shell hooks literally just run the code in your current shell session. It's equivalent to you typing the commands in after mise runs. I don't think there is way to do that without also exposing the env var to your shell. I suppose we could add it then remove it to clean up, but I think the best option is just for you to set a different env var for the project root.

[AndydeCleyre]

OK, is the value somehow available in the context of setting env vars in the config, so we could add

[env]
MISE_PROJECT_DIR={PROJ}

I don't want to hard-code a project dir, so that I can reuse snippets/files.

If the above isn't possible, I guess we could use mise cfg ls -J in the script, and do some JSON parsing, and require a JSON parser.

[AndydeCleyre]

I'll note that in zsh-autoenv, $0 evaluates to the full path of the .autoenv.zsh file, while in mise's case the value is zsh (or possibly sometimes -zsh).

EDIT: source vs eval I guess. I don't know if there were reasons to choose eval over source in mise's case. Well I guess it wouldn't eval the toml, so there's that.

[AndydeCleyre]

Oh! It seems we can use the tera templates in the script value, so I can just use {{config_root}}.

Unless I'm missing something, that seems great and this discussion can be closed. Thanks!

[jdx]

great idea