What is EditorConfig?
EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readable and they work nicely with version control systems.
What's an EditorConfig file look like?
(A formal specification of EditorConfig is also available.)
Below is an example
Check the Wiki for some real-world examples of projects using EditorConfig files.
Where are these files stored?
When opening a file, EditorConfig plugins look for a file named
.editorconfig in the directory of the opened file and in every parent directory. A search for
.editorconfig files will stop if the root filepath is reached or an EditorConfig file with
root=true is found.
EditorConfig files are read top to bottom and the most recent rules found take precedence. Properties from matching EditorConfig sections are applied in the order they were read, so properties in closer files take precedence.
For Windows Users: To create an
.editorconfig file within Windows Explorer, you need to create a file named
.editorconfig., which Windows Explorer will automatically rename to
File Format Details
EditorConfig files use an INI format that is compatible with the format used by Python ConfigParser Library, but
] are allowed in the section names. The section names are filepath globs (case sensitive), similar to the format accepted by gitignore. Only forward slashes (
/, not backslashes) are used as path separators and octothorpes (
#) or semicolons (
;) are used for comments. Comments should go on their own lines. EditorConfig files should be UTF-8 encoded, with either
LF line separators. EditorConfig files are read top to bottom and the most recent rules found take precedence.
Filepath glob patterns and currently-supported EditorConfig properties are explained below.
Special characters recognized in section names for wildcard matching:
|Matches any string of characters, except path separators (|
|Matches any string of characters|
|Matches any single character|
|Matches any single character in name|
|Matches any single character not in name|
|Matches any of the strings given (separated by commas) (Available since EditorConfig Core 0.11.0)|
|Matches any integer numbers between num1 and num2, where num1 and num2 can be either positive or negative|
Special characters can be escaped with a backslash so they won't be interpreted as wildcard patterns.
Note that not all properties are supported by every plugin. The wiki has a complete list of properties.
indent_style: set to
spaceto use hard tabs or soft tabs respectively.
indent_size: a whole number defining the number of columns used for each indentation level and the width of soft tabs (when supported). When set to
tab, the value of
tab_width(if specified) will be used.
tab_width: a whole number defining the number of columns used to represent a tab character. This defaults to the value of
indent_sizeand doesn't usually need to be specified.
end_of_line: set to
crlfto control how line breaks are represented.
charset: set to
utf-16leto control the character set.
trim_trailing_whitespace: set to
trueto remove any whitespace characters preceding newline characters and
falseto ensure it doesn't.
insert_final_newline: set to
trueto ensure file ends with a newline when saving and
falseto ensure it doesn't.
root: special property that should be specified at the top of the file outside of any sections. Set to
.editorconfigfiles search on current file.
Currently all properties and values are case-insensitive. They are lowercased when parsed. Generally, if a property is not specified, the editor settings will be used, i.e. EditorConfig takes no effect on that part. For any property, a value of
unset is to remove the effect of that property, even if it has been set before. For example, add
indent_size = unset to undefine
indent_size property (and use editor default).
It is acceptable and often preferred to leave certain EditorConfig properties unspecified. For example,
tab_width need not be specified unless it differs from the value of
indent_size. Also, when
indent_style is set to
tab, it may be desirable to leave
indent_size unspecified so readers may view the file using their preferred indentation width. Additionally, if a property is not standardized in your project (
end_of_line for example), it may be best to leave it blank.
No Plugin Necessary
These editors come bundled with native support for EditorConfig. Everything should just work.
Download a Plugin
To use EditorConfig with one of these editors, you will need to install a plugin.
- Sublime Text
- Visual Studio Code
To use EditorConfig with one of these headless tools, you will need to install a plugin.
Contributing to EditorConfig
Give us your feedback
This project is greatly in need of feedback from other developers. We want to hear ideas about how to make this project better. Please use the mailing list to send an email to the EditorConfig team (subscribe by shooting an email to email@example.com) and use the issue tracker to submit bugs (but please take a look at the FAQ first). Also feel free to tweet at us.
Create a plugin
EditorConfig plugins can be developed by using one of the EditorConfig core libraries. The EditorConfig core libraries accept as input the file being edited, find and parse relevant
If you are planning on creating a new plugin, use the mailing list to let us know so we can help out and link to your plugin once it's created. If you plan on using one of the EditorConfig cores as a library or command line interface, the C library documentation, Python library documentation or Java library documentation may be helpful.
More details can be found on the Plugin-How-To wiki page.
- EditorConfig C Core: Hong Xu and Trey Hunner
- EditorConfig Java Core: Dennis Ushakov
- ec4j: Peter Palaga and Angelo Zerr
- EditorConfig Python Core: Trey Hunner
- EditorConfig .NET Core: Martijn Laarman
- EditorConfig Ruby Core: Joshua Peek and Brian Lopez
- Atom plugin: Sindre Sorhus
- Brackets plugin: Chen-Heng Chang
- Code::Blocks plugin: Hong Xu
- Emacs plugin: Trey Hunner, Johan Sundström, 10sr
- Geany plugin: Hong Xu
- Gedit plugin: Trey Hunner
- GitHub Browser extension: Ingvar Stepanyan
- JetBrain plugin: Kevin Bell, Dennis Ushakov
- jEdit plugin: Hong Xu
- Micro plugin: 10sr
- NetBeans plugin: Benny Neugebauer, Michael Koppen, Junichi Yamamoto
- Notepad++ plugin: Hong Xu
- Sublime Text plugin: Sindre Sorhus
- TextMate plugin: Rob Brackett
- Vim plugin: Hong Xu, Trey Hunner
- Visual Studio plugin: William Swanson, nulltoken, Martijn Laarman, Arkadiy Shapkin, Jed Mao
- Visual Studio Code extension: Jed Mao, Chris Dias
- Xcode plugin: Marco Sero