jdx

I think this would be better: ```toml [[env]] _.file = {path = 'defaults.env'} # in version control [[env]] _.file = {path = '.env', optional = true} # not in version...

I think some support was put into the codebase recently that allows each core plugin to do its own resolving logic making it possible to support things like `ruby@truffleruby+graalvm-24` which...

@ylluminate might be asking for that but I don't think he actually has any need for that. I think the more important gap in mise is that you can't run...

yeah we should probably put `fuzzy_match_filter` on the trait so we don't need to do that

deadlocking certainly sounds like a possibility when attempting to install the same tool. mise uses some lockfiles that should prevent such a situation that I believe will output extra information...

@pepicrft really sorry it took me so long to get around to this. It looks excellent though. I had some feedback that really is just nitpicks pretty much. The one...

I think I figured out a decent way forward. I just put some docs on how to disable the rc files with bash or zsh. I think that's better than...

You can already call tasks defined in other loaded config files. I suppose the goal here is to have something like a monorepo setup where the base config can call...

this may be the root cause why the "short circuiting" logic isn't working in https://github.com/jdx/mise/issues/1617. I have not investigated but I suspect the short circuiting logic is still incorrectly calling...

~~this is impossible. mise would need to wrap every command but that simply is not how it works~~ edit: sorry I misunderstood, I thought you were asking when something is...