Open iancward opened 3 months ago
This is a "known issue", though your success with ASCII is a useful tidbit. UTF-8 was failing too. Normally I'd mark this as a duplicate, but I think this is an important point, so I'll keep this open until I can figure out a fix. There are some challenges with ASCII I'll need to think through.
In PowerShell, the >
operator effectively maps to Out-File
, so to work around this, we switched to | Out-File -Encoding ascii
.
What happened?
We did the "noinstall" deployment method and generated
settings.txt
with PowerShell. Apparently this caused the file to be generated with UTF-16LE, which is the default encoding by PowerShell.Running
nvm list
causes this issue:We had to convert
settings.txt
toascii
because even as UTF-8, it didn't work.What did you expect to happen?
I expected that NVM should work. Although I understand that UTF-16LE isn't exactly a common (outside of PowerShell) encoding scheme.
Version
1.1.11 or newer (Default)
Which version of Windows?
Windows 10 (Default)
Which locale?
English (Default)
Which shell are you running NVM4W in?
PowerShell
User Permissions?
Administrative Privileges, Elevated
Is Developer Mode enabled?
None
Relevant log/console output