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
Interesting seeing this again. I previously merged #1561, which (was supposed to) print a warning message when this happened. I guess on some code paths it's not activated. It might be worth looking into automatically fixing the file, but if I remember correctly, we decided that a warning message will suffice.
Ran into this problem with version: v0.14.0-ccdd47d where a docker container is run by mounting a windows dir where files are naturally in CRLF mode. A lot of time was wasted.
Could this be solved by "teaching" asdf to work with CRLF and not just LF?
Describe the Bug
Somehow, I had a
.tool-versions
with its lines ending in CRLF (\r\n
), and that didn't sit well with asdf.See output below:
Steps to Reproduce
\n
ending:printf 'nodejs 14.7.0\n' > .tool-versions
xxd .tool-versions
asdf current
. Should work as usual.\r\n
ending:printf 'nodejs 14.7.0\r\n' > .tool-versions
xxd .tool-versions
asdf current
. Its output should get broken fornodejs
.Expected Behaviour
I don't think asdf should take care of blank lines or particular line endings.
Actual Behaviour
Should work regardless of
\r\n
and\n
.Environment
(Some parts below have been redacted for privacy.)
asdf plugins affected (if relevant)
The text was updated successfully, but these errors were encountered: