feat: mise hints

[roele]

First draft for a very pragmatic approach on mise hints. Just adds a simple hint! macro with static args which respects the setting. Since i wasn't able to figure out yet how to have a multi-type setting i thought it might be handy to use disable_hints= ["*"] as a way to disable all commands (IIRC we use * for running all tasks as well?)

It might be nicer to have something which we could pin to the run method such as #[hint(...)] (derive, proc_macro?). Not sure if Rust has something similar to Aspects in Java which allows you to run stuff after/before method calls etc.

Still a bit undecided about the styling. We probably should stick to a dim prefix like info messages but should highlight the command somehow with bold?

Fixes #2460

[jdx]

I like the *!

[jdx]

I think a great addition to this would be the current warning about precompiled python binaries which is probably annoying to people that already are aware of its limitations

[jdx]

We can actually probably just remove this file

[roele]

was already wondering if this is still useful since all settings can also be part of .mise.toml

[roele]

@jdx tried to disable the hints for the tests but one test keeps failing and i can't figure out why. it passes in my IDE and when run via cargo test but not via nextest.

--- TRY 3 STDOUT:        mise::bin/mise cli::install::tests::test_install_nothing ---

running 1 test
test cli::install::tests::test_install_nothing ... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Summary ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Snapshot file: src/cli/snapshots/mise__cli__install__tests__install_nothing.snap
Snapshot: install_nothing
Source: src/cli/install.rs:193
────────────────────────────────────────────────────────────────────────────────
Expression: output
────────────────────────────────────────────────────────────────────────────────
+new results
────────────┬───────────────────────────────────────────────────────────────────
          0 │+mise hint install multiple versions simultaneously with mise install python@3.8 python@3.9
────────────┴───────────────────────────────────────────────────────────────────
To update snapshots run `cargo insta review`
Stopped on the first failure. Run `cargo insta test` to run all snapshots.
FAILED

failures:

failures:
    cli::install::tests::test_install_nothing

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 233 filtered out; finished in 0.12s

[roele]

Is it just me or does this feel a bit annoying and intrusive? How would we educate users about disabling the hints?
Maybe something interactive (confirmation/dialog) which disables it after confirmation would be easier to use and more tolerable? Or maybe i am overthinking this again and we should start simple...

[roele]

i wonder if we need more fine grained control here

[jdx]

yeah I think we should show a second line like: mise hint disable this thing with "mise settings set ..."

[roele]

it's a bit unfortunate that array settings are not additive, so we need to include existing settings mise settings set disable_hints install,plugins otherwise it would overwrite a disable_hints = ["plugins"] instead adding to it.

[jdx]

yeah maybe at some point we could add a mise settings add disable_hints or something