Add EOL option

[egamma]

twitter thread https://twitter.com/domenic/status/697921719529398272

[stkb]

+1 An option to change the default on Windows would be nice.

[egamma]

[glen-84]

Duplicate of #1546?

[alexdima]

639a3cb

[egamma]

@alexandrudima i'll add this to the feb plan, so that we do not forget to release note the feature

[edgariscoding]

Is there a way to set LF line endings as default?

I looked in Preferences > User Settings but didn't see a setting for this.

My Surface + Visual Studio Code are used as extensions of my Linux/Mac environment. I'll never need CRLF so I have to constantly change from CRLF to LF when I create new documents. If I forget to do this it causes trouble.

[glen-84]

@edgr-sanchez

"files.eol": "\n"

[edgariscoding]

@glen-84

Perfect, thank you!

[ghost]

@glen-84
nice job! thanks

[smithyj]

thank you @glen-84

[tharrison159]

I have "files.eol": "\n" set in my user preferences but whenever I open a project it always defaults to clrf, any ideas why it's still doing this?

[smithyj]

@tharrison159 yes，a project in vscode it always defaults to crlf, because vscode set user preferences is into a project

[tharrison159]

I am working on a project that is shared between unix systems and windows so the line breaks need to be LF not CLRF, is there anyway to convert the whole project to LF?

[smithyj]

use git and set git config --global core.autocrlf true / false / input

[smithyj]

@tharrison159 What are your FB account or TW account

[jsilvermist]

This should be better documented, nothing comes up when searching for lf or crlf in the settings.

[alexdima]

Pushed a change to improve the documentation

[strattonbrazil]

Something that's not entirely obvious to many, but it seems that if there are already CRLFs in the existing file, VSC will fallback to using those. After seeing CRLFs introduced in the change log, I tried a different file and didn't see them added. I also saw in settings it was already set to use LF. When I ran dos2unix on the offending file and then when back and added a new line, I no longer saw the CRLFs. This seems to match the functionality I've seen on some other editors.

TL;DR If you're seeing CRLFs and your settings are using LF, you might need to remove the existing CRLFs in the file or else the editor will fall back to using those for consistency across lines.

[grobmeier]

Actually @strattonbrazil is right. I had the same problem: there was a CRLF in a css file which caused VSC to write CRLF, even when I had "files.eol": "\n",

Running "dos2unix" fixed the problem entirely. The git config didn't help, it just fixes the changed lines (I think)

[rsmolkin]

So I'm having the same problem. Working on a team where some have Macs and some have Windows. My files.eof is set to "\n" but every time I open a file it still shows crlf in the bottom blue bar and my eslint freaks out, so I have to change it every time I open a file. How can we set this to be default not just on new files but for every file in a project?

[drkmullins]

Was having similar issues to @rsmolkin and seemed to resolve it by adding *.js text eol=lf
to my .gitattributes file as mentioned in the linebreak-style rule docs

[rsmolkin]

@drkmullins Thanks for the find. Can you clarify if this is for the global Git directory where Git is installed, or local to each project in the .git/info/ directory. The only file I see in there is exclude, but I guess I can add .gitattributes with that one line in it?

[bialix]

Is it possible to configure line-endings settings per file type? E.g. LF for python files, but CRLF for batch files?