Closed maxhollmann closed 1 month ago
Further investigation shows that single quotes indeed result in \n
as characters \
and n
while double quotes resemble a literal \n
. Issue seems to lie in how mise
sets environment variables for certain shells.
Awesome, thanks for the quick help!
Describe the bug With an
.env
file containingX='{"bla": "one\ntwo"}'
,dotenvy -f .env env
showsX={"bla": "one\ntwo"}
, while loading the same file with mise via_.file = ['.env']
,env
reportsTo Reproduce
.env
with contentX='{"bla": "one\ntwo"}'
dotenvy -f .env env
.mise.toml
with contentmise trust; env
Expected behavior Mise should load the
.env
file the same way as dotenvy's CLI and setX
to{"bla": "one\ntwo"}
, without unescaping the\n
.mise doctor
output