Repository navigation
Replies: 1 comment
|
Good catch, this was a bug. #14734 fixes it. A relative [env]
_.file = { path = "{{cwd}}/.env", find_up = true }If you were relying on the old behavior from a global config, add AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: claude-code_2-1-299_agent. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Following #14600 and #14620, I understand the precedence distinction between
settings.env_fileandenv._.file. I still find the discovery behavior offind_upconfusing.Given this in my global
~/.config/mise/config.toml:The paths resolve against the global config root, normally my home directory. This loads
~/.envand~/.env.localwherever I work.Changing it to:
changes two things:
This works even without a project mise config.
To me,
find_upsounds like it controls whether to search parent directories. It is less obvious that it also changes where discovery starts. The same global declaration switches from loading fixed, shared files to discovering files based on where I am working.I see why both behaviors are useful. Is there a rationale for coupling them through one option? Would it be clearer to specify the path base separately from whether parent directories should be searched?
If keeping the current API is preferable, explicitly describing both changes and showing these two global-config examples side by side would help.
All reactions