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
Does this issue occur when all extensions are disabled?: Yes
VS Code Version:1.68.0-insider (user setup)
OS Version:Windows_NT x64 6.1.7601
Steps to Reproduce:
1.create a file, line end with LF and contain CR.
i.e. echo -e 'aaa\rbbb\nccc\n' > 1
2. edit with vscode, input or delete words
3.save
4.CR was replaced by LF.
usually, this replacement takes no effect. but I have a shell script in which CR is a separator of awk command. once CR was replaced by LF, the script run into error.
The text was updated successfully, but these errors were encountered:
VS Code is currently very opinionated about line endings and tries to "fix them" as best as possible to make the problem of mixed line endings a thing of the past. This, however, comes at the cost that it ends up touching areas of the text buffer that are not edited directly.
I suggest we track this in not identical, but similar issues, #127 or #35797 .
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
1.create a file, line end with LF and contain CR.
i.e.
echo -e 'aaa\rbbb\nccc\n' > 1
2. edit with vscode, input or delete words
3.save
4.CR was replaced by LF.
usually, this replacement takes no effect. but I have a shell script in which CR is a separator of awk command. once CR was replaced by LF, the script run into error.
The text was updated successfully, but these errors were encountered: