Please, add a menu/option to disable/enable enforcing EditorConfig functionality (i.e. enforcing .editorconfig settings) without loosing syntax highlighting.
There are times when it might be useful to bypass the .editorconfig settings of a third party project (especially because EditorConfig doesn't support end_of_line = native — see editorconfig/editorconfig#226).
Yet, it would be nice to keep at least syntax highlighting of .editorconfig files, when disabling EditorConfig functionality, because most likely one is disabling itdue third party settings in the project which are somehow conflicting with the local setup (e.g. a third party project being worked on in a new repository with different .gitattributes settings) and will be editing the .editorconfig file to tweak those settings.
This package provides both EditorConfig functionality and syntax higlighting, so it should make sense to be able to toggle on/off the former without loosing the latter, treating them as two independent parts of the package.
Please, add a menu/option to disable/enable enforcing EditorConfig functionality (i.e. enforcing
.editorconfigsettings) without loosing syntax highlighting.There are times when it might be useful to bypass the
.editorconfigsettings of a third party project (especially because EditorConfig doesn't supportend_of_line = native— see editorconfig/editorconfig#226).Yet, it would be nice to keep at least syntax highlighting of
.editorconfigfiles, when disabling EditorConfig functionality, because most likely one is disabling itdue third party settings in the project which are somehow conflicting with the local setup (e.g. a third party project being worked on in a new repository with different.gitattributessettings) and will be editing the.editorconfigfile to tweak those settings.This package provides both EditorConfig functionality and syntax higlighting, so it should make sense to be able to toggle on/off the former without loosing the latter, treating them as two independent parts of the package.