fix(nushell): cannot switch version

[bytemain]

@colececil

because here we change the nushell config, so you need to restart twice to make the latest config work, or you will see an error.

[colececil]

Thanks, @bytemain! Switching versions with vfox use is working for me too now with this change. Awesome! 🎉

However, it seems it's still not taking into account .tool-versions files. For example:

~> node --version
v22.12.0
~> cd `Git Repos\`
~\Git Repos> open .tool-versions
nodejs 20.18.3
~\Git Repos> node --version
v22.12.0

And here's the same thing in Git Bash:

~$ node --version
v22.12.0
~$ cd Git\ Repos/
~/Git Repos$ cat .tool-versions
nodejs 20.18.3
~/Git Repos$ node --version
v20.18.3

[colececil]

FYI, I'm also getting intermittent issues with Nushell not finding executables in directories that vfox adds to my path, but I think this is a Nushell issue if I understand correctly. I'm not sure if this behavior is specific to Windows. See my comment at nushell/nushell#7741 (comment).

[aooohan]

LGTM.

[bytemain]

Thanks, @bytemain! Switching versions with vfox use is working for me too now with this change. Awesome! 🎉

However, it seems it's still not taking into account .tool-versions files. For example:

~> node --version
v22.12.0
~> cd `Git Repos\`
~\Git Repos> open .tool-versions
nodejs 20.18.3
~\Git Repos> node --version
v22.12.0

And here's the same thing in Git Bash:

~$ node --version
v22.12.0
~$ cd Git\ Repos/
~/Git Repos$ cat .tool-versions
nodejs 20.18.3
~/Git Repos$ node --version
v20.18.3

let me check

[colececil]

FYI, I'm also getting intermittent issues with Nushell not finding executables in directories that vfox adds to my path, but I think this is a Nushell issue if I understand correctly. I'm not sure if this behavior is specific to Windows. See my comment at nushell/nushell#7741 (comment).

Based on discussion at the link above, it sounds like the workaround is to use Path with load-env on Windows, while continuing to use PATH on other operating systems. I can get a separate issue created for this, and I should be able to create a pull request this week to fix it.