.editorconfig: do not specify line ending

[andreynering]

That is annoying on Windows, since the editor will change the file if you just open it. Git will checking as LF anyway.

[codecov-io]

Current coverage is 3.03% (diff: 100%)

Merging #171 into master will not change coverage

@@            master      #171   diff @@
========================================
  Files           33        33          
  Lines         8096      8096          
  Methods          0         0          
  Messages         0         0          
  Branches         0         0          
========================================
  Hits           246       246          
  Misses        7830      7830          
  Partials        20        20          

Powered by Codecov. Last update 81f227e...a285c07

[tboerger]

I don't understand why windows should change anything if your editor respects this setting?

[thibaultmeyer]

That the point. This PR remove the setting who force Windows to use LF rather than CRLF.

[tboerger]

I don't have a strong opinion on that, I'm anyway using my Sublime settings. LGTM

[strk]

@andreynering are you sure git will check in as LF anyway ? Why would it do do ? (I see something in .gitattributes but I'm not sure how that work)

[andreynering]

Yes, Git by convention on Windows, checkout as CRLF and check-in as LF.

When you have LF on editorconfig, and you open any file, the editor will convert from CRLF to LF, and git status will think all these files changed.

The right think it's just use the default ending of the OS.

[metalmatze]

LGTM