Describe the bug
This is technically two things, but both related to setting PATH in nushell. I have a fix locally, but am having some trouble getting the docker tasks to run, so opening an issue before I spend time on the tests.
If mise is not in the path when mise activate nu is run, it will prepend
Describe the bug This is technically two things, but both related to setting
PATH
innushell
. I have a fix locally, but am having some trouble getting the docker tasks to run, so opening an issue before I spend time on the tests.If
mise
is not in the path whenmise activate nu
is run, it will prependto the output. This causes an error
The solution is to use
export-env
:Related, the current method of setting
PATH
for installed tools breaks the table-like output expected innu
:instead of
To Reproduce
mise
not in PATH, run the setup instructions here: https://mise.jdx.dev/getting-started.html#nushell, but make sure to use the full path tomise
.use
command to load the module created above.Expected behavior A clear and concise description of what you expected to happen.
mise doctor
outputAdditional context There is a relatively simple fix to both items:
Happy to open a PR if I can get the docker tasks to run.