Align file-selection CLI option between use and set

[glasser]

The two things I tend to put in mise.local.toml most often are tool versions and environment variables, and they are also things I like setting with the CLI rather than just editing the files directly. But how to accomplish this is different across the commands.

For mise set, you can run mise set --file=mise.local.toml FOO=bar. mise set --env local FOO=bar does not cause it to write to mise.local.toml, and --path does not work.

For mise use, you can run mise use --path=mise.local.toml foo@bar, or mise use --env local foo@bar. --file does not work.

I think the simplest suggestion I have is that --file and --path should be synonyms in both commands.

Perhaps mise set --env=local FOO=bar should work as well, though that's more of a back-compat concern.

[JamBalaya56562]

Your suggestion shipped, and then some: --file and --path are now synonyms on every command that names a config file, not just the two this discussion mentions.

PR	commands
#11577	use, set — the pair you named
#11616	unuse, unset
#11631	dotfiles add, bootstrap packages use, bootstrap packages import, bootstrap packages brew tap, bootstrap packages brew untap
#11640	config get, config set

All merged 2026-08-02. Not in a release yet — v2026.8.0 was cut a few hours before the first of them, so they land in the next one. A clap-introspection test in src/cli/mod.rs now asserts the alias exists on all eleven, so a new command can't quietly reintroduce the split.

It took a detour worth recording, since this sat for over a year with no reply. @Marukome0743 implemented it in #11116, and it was closed the next day with no review comments at all. Worth being precise about what that PR was: it covered exactly the eleven commands above — same files, same change. So the objection was pacing, not the idea, and the end state is the one that PR proposed, reached in four merges instead of one.

config get and config set needed one extra thing along the way. They were also the only two that rejected a directory, so mise config set --path ./some-dir key=value died on a bare Is a directory (os error 21) while use, set, unuse and the rest resolved it to the config file inside. #11640 routes them through the same resolver, so a directory now works there too and a path that resolves to nothing says so instead of surfacing an io error.

Your second point is already handled, and has been for a while — measured on v2026.7.15:

$ mise set --env local FOO=bar
$ cat mise.local.toml
[env]
FOO = "bar"

mise set passes --env through to the same target resolver mise use uses, so -E/--env local writes to mise.local.toml as you expected.