If an .editorconfig file were found, would it apply those changes over the defaults or just on their own? For example, if the default tab_width was 4 and I have an .editorconfig file with trim_trailing_whitespace = true, is it going to also inherit the default tab_width of 4?

Furthermore, what do you do in cases where there are multiple .editorconfig files in the project? There can be more than one and they all may or may not have root = true.

Would it be possible to support internal GitHub Enterprise installations?

I've recently tried this plug-in (github's native support doesn't seem to work for us) as we were trying to change the way GtHub displays tab sizes. I created a stackoverflow question (http://stackoverflow.com/questions/33892410/editorconfig-file-in-github/) and it was suggested I mentioned this here.

I created an .editorconfig file which I stuck at our repo's root:

# top-most EditorConfig file
root = true

#4 space indentation
[*.{cpp,h,cs,xaml,editorconfig}]
indent_style = space
indent_size = 4

This works great if we go look at a file in GitHub, however if we are looking at the revision comparison view (such as when going through a pull request review) the tabs still display in their original 8 spaces. I'm not sure if this is a known limitation, or if it just isn't working for us, but for us this is the main reason we got excited about this tool and it was a bit sad to see it didn't work.

Thanks, and any information on this would be welcome!

https://addons.mozilla.org/en-US/firefox/addon/github-editorconfig/ is not found?

Does this plugin only support indentation (in both view and edit mode)?

If so indent_style/indent_size (and possibly tab_width) should be listed as supported in the README file (similar to the way the other plugins list support).

Nobody wants a tab_width of 8.

I'd like to use the plugin in Safari for OS X.
Could you add support please?

This was released last week and I plan to tweet about it soon.

You can verify this by disabling the extension and viewing/editing files in projects with .editorconfig files.

The code viewer is for viewing code and I don't think the repo project should decide how I view its code.

Applying to the editor makes sense, but for the code viewer it should be some default values. Might add an option page to change them. The code viewer should not be affected by the .editorconfig config.