Splitting main hook/activation from mise.toml:hooks.enter/hooks.leave activation?

[AndydeCleyre]

I'm wondering if this might be possible now, or in the future.

The issue is some tricky sequencing in my Zsh startup files:

Periodically I want some arbitrary programs to (re)generate their shell completion definitions.

These actions place files in an fpath folder, and so should be done before compinit is called, which loads fpath contents. Some of these programs are installed via mise, so these actions should happen after mise's "main" activation.

Some Zsh plugins need to be sourced after compinit is called, so that the completion system is available.

A mise.toml's hooks.enter and hooks.leave can use these Zsh plugins (with shell = "zsh"). So these hooks should be called after the Zsh plugins are sourced.

So would it be possible to have a sequence like:

• activate mise, excluding mise.toml hooks.enter and hooks.leave
• do things with mise-installed tools
• compinit
• load functions which might be used in hooks.enter and hooks.leave
• activate/alter mise hooks to enable hooks.enter and hooks.leave

?

[AndydeCleyre]

Can you help me understand the workings of _mise_hook? When I try to inspect the output of mise hook-env -s zsh manually, it's always empty.

But AFAICT there's a single hook function that handles all hook actions, at least at the external interface.

Would it be possible for me to write my own hook functions invoking mise, so that the ones for changing the environment could be in one, and the ones for running tasks in another, so that I can add them to Zsh's chpwd hook array at different times?