You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using nvs on a windows machine. After I configured my git git config --global core.eol lf and git config --global core.autocrlf input I still get this error in Git Bash when I try nvs use latest or nvs use node/version:
...user/AppData/Local/nvs/nvs_tmp_1733440591.sh: line 1: unexpected EOF while looking for matching ...user/AppData/Local/nvs/nvs_tmp_1733440591.sh: line 3: syntax error: unexpected end of file.
(Before git configuration everything worked fine)
This should occur because of CRLF vs LF line endings. To solve this I tried dos2unix nvs.sh to convert line endings to LF, but the problem is that line endings still be CRLF (as I understood) in that temporary generated files by nvs.sh (post executable scripts). Is there any way to apply dos2unix also on that temp generated files? Or maybe do you have other ideas how to solve this problem? Thanks
The text was updated successfully, but these errors were encountered:
Hello there,
I am using nvs on a windows machine. After I configured my git
git config --global core.eol lf
andgit config --global core.autocrlf input
I still get this error in Git Bash when I trynvs use latest
ornvs use node/version
:...user/AppData/Local/nvs/nvs_tmp_1733440591.sh: line 1: unexpected EOF while looking for matching
...user/AppData/Local/nvs/nvs_tmp_1733440591.sh: line 3: syntax error: unexpected end of file
.(Before git configuration everything worked fine)
This should occur because of CRLF vs LF line endings. To solve this I tried
dos2unix nvs.sh
to convert line endings to LF, but the problem is that line endings still be CRLF (as I understood) in that temporary generated files by nvs.sh (post executable scripts). Is there any way to apply dos2unix also on that temp generated files? Or maybe do you have other ideas how to solve this problem? ThanksThe text was updated successfully, but these errors were encountered: