Replies: 1 comment
-
I think it should behave as you expected |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently, I use
mise activate
in my shell and expect mise to do it's thing when Icd
into a project with amise.toml
.I've been thinking about a more explicit activation of mise and came across
mise en
in the 2025 announcement. Agree on the command name BTW. :o)Anyway, I was expecting
mise en
to work like this:with my goal being a shell opened to that directory, configuration in
~/projects/foobar/mise.toml
applied, and tasks in that directory available. The equivalent end-result being what I would have had withmise activate
+cd ~/projects/foobar
.But that didn't work as expected and, upon reading the docs further, saw that the command "starts a new shell with the mise environment built from the current configuration."
So I need to do instead:
I'm not sure what the use case is for opening a new shell with the current path's configuration while ignoring the configuration in the target directory. But, could
mise en
be enhanced so it takes into consideration configuration in the target directory?If there is a use case for ignoring target directory configuration, maybe that can be an option instead of the default?
mise en --ignore-config ~/projects/foobar
Beta Was this translation helpful? Give feedback.
All reactions