-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display mixed line endings explicitly in status bar as "LF (mixed)" or "CRLF (mixed)" #119025
Comments
You might also want to display a confirmation dialog when saving, before auto-fixing the mixed line-endings, just to avoid unexpected/unwanted automatic behavior when user is just doing a simple edit operation (specially if they happen to open a binary file as text). The confirmation dialog could have buttons |
Yes, I'm sure it's useful. a file contains a LF CRLF mix of cases, and I don't want to convert to a particular one in exceptional cases |
When a file contains a mixture of lf and crlf, I don't want to change any lf or crlf changes when I save and format the code, but now the reality is that it changes automatically |
I also find it useful, especially when it comes to git code, always thinking that I have changed a lot of places. |
Not having the ability to show newlines, CR/LF, EOF is bad for both beginners and experienced developers. I mention this because there is a lot of positioning of vScode as a solution for beginners. |
any plan on this feature |
Still nothing? |
I'd still really like this. It is a feature of Visual Studio I really miss in VSC |
When opening a file with mixed line endings, vscode is still showing it as⚠️ icon) until the file is modified.
LF
orCRLF
in the status bar.After saving, it fixes it, but I think it should show, for example,
LF (mixed)
(maybe with squiggle orThis is important so that you know the file still has mixed EOLs, and you might want to fix that.
To reproduce:
printf "lf\ncrlf\r\ncr\rnone" > mixed-eol.txt && code mixed-eol.txt
If you open this file in Notepad++ and enable visible EOL, you can see it has mixed endings.
(Posted from #12223 (comment) as separate issue.)
The text was updated successfully, but these errors were encountered: