Files being changed even when all rules are met and no changes are made

Steps to reproduce

Editor config:

root = true
[*]
indent_style = space
indent_size = 4
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
[*.md]
trim_trailing_whitespace = false

Versions: EditorConfig extension: 0.3.4 VSCode: 1.8.1

Steps:

• Open a file
• Being asked to save

Expected Behavior

Should not be asked to save.

Actual Behavior

The file is being asked to save.

[jednano]

@kowsheek some Windows Git distributions (e.g., GitHub for Windows) configure your system to automatically convert line endings from LF to CRLF when files are checked out. This line-ending conversion is controlled by a Git configuration flag: autocrlf.

There is some controversy regarding the best value for autocrlf; however, having CRLF line endings will cause issues like the one you’ve just experienced. As such, I recommend configuring your repositories such that they never convert line endings.

To disable automatic line-ending conversion, you should visit each of your repositories and execute the following commands:

git config core.autocrlf false
git rm --cached -r .
git reset --hard

The first command tells Git to never change line endings (in the future). Next, we refresh each repository by removing every file from Git’s index and, finally, rewriting the Git index to pick up all the new line endings. This fixes the CRLFs that were introduced to your local file system when you cloned each repository.

Now, you can work in LF mode via EditorConfig and never introduce rogue CRLFs into your files.

You can also run git config core.autocrlf false --system to change the system-wide setting, which is actually what I do on Windows so I don’t have to deal with this on a regular basis.

[kowsheek]

I didn’t need to remove .gitattributes which I use in my repo to specify binaries such as favicons. I did the global and local setting changes to get it rolling.