Frank Fesevur

> Personally i really expect any editorconfig-rule to be applied exactly the same way in every different tool. Except a rule cannot be implemented because of limitiations within implementing environment....

Looking back at the commits, @ViceIce has added these (apart from this small but annoying issue) beautifully working scripts. Maybe he has an idea how to solve this issue.

You are right that there is no support for `charset` at this moment. But note that `charset` is not mentioned as a [Supported properties](https://github.com/editorconfig/editorconfig-notepad-plus-plus#supported-properties). That said, you are right that...

Dutch is my native language, so I don't run into those encoding problems much. I have never had any problems with Notepad++ detecting the encoding of a document. But as...

Supporting `-*- encoding` is not related to this plugin. It is different functionality. What you are looking for is support for Emacs File Variables. Funnily enough, it is a concept...

In general I like the idea. But what about security? Are absolute paths allowed, or required? Is `..` allowed? If so, how many levels deep? Should be able to get...

Don't see how ignore lists of spell checkers can be editor independent. Editors all their own implementation and therefore file formats. And those files are stored far away in users...

I think it is great the VS2017 has builtin EditorConfig support. The release notes are about the RC. Those limitations you mention **may** even be fixed in the RTM.

Although I haven't tested the RC, I assume it is a Visual Studio feature, not a language specific one. So it should work for all languages that VS supports.

As said, haven't seen it in action yet but I assume when you put the .editorconfig file in the right place (the root directory of your solution) it will work...