VSCode Makefile `spaces` not converted to `tab` on save

[tljstewart]

# https://editorconfig.org/

root = true

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

# Docstrings and comments use max_line_length = 79
[*.py]
max_line_length = 88

# Use 2 spaces for the HTML files
[*.html]
indent_size = 2

# The JSON files contain newlines inconsistently
[*.json]
indent_size = 2
insert_final_newline = ignore

[**/admin/js/vendor/**]
indent_style = ignore
indent_size = ignore

# Minified JavaScript files shouldn't be changed
[**.min.js]
indent_style = ignore
insert_final_newline = ignore

# Makefiles always use tabs for indentation
[Makefile]
indent_style = tab

# Batch files use tabs for indentation
[*.bat]
indent_style = tab

[docs/**.txt]
max_line_length = 79

[*.yml]
indent_size = 2

[AnrDaemon]

Indentation is only fixed on source formatting. Try setting "Format: on save" for example.

[shoulders]

Indentation is only fixed on source formatting. Try setting "Format: on save" for example.

So the following settings are only advisories to the editor and are applied going forwards, it will not affect any current indentations etc..

indent_style
indent_size
tab_width

For me this is expected behaviour that pre-existing indentations are converted to match your editorconfig settings.

[AnrDaemon]

Which would make an unnecessary noise when applied to pre-existing files under version control.

[shoulders]

Noise is irrelevant for version control.

Essentially you would at most only have one mass event then the rest of the coding will stay as per the settings in editorconfig.

This also assumes a user would not use another application to do the tidying such as prettier or biome.

[AnrDaemon]

Sorry, but that's very relevant for a large codebase.

[shoulders]

Because your codebase is large you do not need code consistency throughout, then what is the point in code consistency at all.

Might as well not use editorconfig.