Given the potential conflicts of storing different per-project beautifier settings for the same file, the
.editorconfig solution of specifying file formatting information in a separate settings file in the directory (or parent directory) where the edited file is found seems better.
As I wrote above in this thread, simply ensure that, once such
.editorconfig type files are made active in SE's Options, anything specified in those options file (or parent files) overrides equivalent general formatting options, and then everyone will be able more or less to keep track of what's going on.
Maybe to make sure users can easily find out what formatting options are being applied, a UI similar to the adaptive format statistics dialog would show them and the
.editorconfig file where they were found... assuming that the SE
.editorconfig feature is implemented as described in the
standard. (Is it?)
Those kind of
.ini format files arealso easier to read than
XML, and easier to manage visually in version control scenarios.
Just my 0.2 cents...
UPDATE: Clark's posting below invalidates what I wrote above. Lack of analysis of wider SE application context, etc., etc...