Proper fix for line endings

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Describe the feature you'd like. --> Hi, i found out, there can be set preferred line ending. But issue i found is, how it is behaving on wrong line endings. To provide a specific example, its a misbehaving of some ftp servers. I found very helpful description of the issue on WinSCP site: Pure-FTPd FTP server: When downloading a file with Windows line-endings (CR+LF) in a text/ASCII mode, the server replaces LF with CR+LF, resulting in an incorrect **CR+CR+LF**. When opening such file in an Internal editor of WinSCP (or **VSCode too**), the **editor interprets the sequence as two line endings (CR and CR+LF)** resulting in a blank line after each and every content line. When the file is saved, the internal editor saves two Windows line endings CR+LF and CR+LF. On upload they get converted to two LF’s. It seems, VS code has the same 'bug' - falsely expecting it to be 2 newlines. So, obviously, a nice fix would be, on opening the file, if a combination of CR+CR+LF is found within, then expect it to be from bad server, and replace it for either only one LF, or one CR+LF (removing the first CR) Recently i had a much problems working on such server, using WinSCP + VSCode as external editor. I found quick fix would be using only binary mode even for text files, and setting VSCode to use LF (\n) only. But i believe this is a pretty generic case to fix that behaviour (if anyone can provide a scenario where on windows someone intentionally needs **CR+CR+LF** line endings, please leave a comment too) if it would be a possible issue, maybe basing on filetype it could have additional fixes - i can imagine unexpected line merging may cause issues for example for slingle-line comments in JS or PHP, or other files, bc next line may get commented... but so…