- Bug #236
openFix CRFL
0%
Description
I noticed that the CRFL ought to have been CRLF (the LF part meaning "line feed". But while checking for a published standard on this I read here: https://medium.com/@andrekardec/fixing-expected-linebreaks-to-be-lf-but-found-crlf-in-vscode-2023-42d7c518e71d ...that:
Windows uses the Carriage Return (CR) and Line Feed (LF) characters together as the EOL sequence. This is because early computer systems used mechanical teletypewriters that required both CR and LF to move the print head back to the left margin and advance the paper to the next line.
Unix-based systems, on the other hand, including Linux and macOS, use only the Line Feed (LF) character as the EOL sequence — Unix was influenced by the use of electronic typewriters, which only required the LF character to move to the next line.
Oh.
Well then let's do the UNIX thing and use "LF" only.
I set this as "urgent" only because it is so simple to do, yet removes both a typo and a Windows artifact!