Special characters recognized in section names for wildcard matching: * EditorConfig files are read top to bottom and the most recent rules found take precedence.įilepath glob patterns and currently-supported EditorConfig properties are explained below. EditorConfig files should be UTF-8 encoded, with either CRLF or LF line separators. Only forward slashes ( /, not backslashes) are used as path separators and octothorpes ( #) or semicolons ( ) are used for comments.
The section names are filepath globs (case sensitive), similar to the format accepted by gitignore. File Format DetailsĮditorConfig files use an INI format that is compatible with the format used by Python ConfigParser Library, but are allowed in the section names. (note the trailing dot), which Windows Explorer will automatically rename to.
editorconfig file within Windows Explorer, you need to create a file named. Properties from matching EditorConfig sections are applied in the order they were read, so properties in closer files take precedence.įor Windows Users: To create an. editorconfig files will stop if the root filepath is reached or an EditorConfig file with root=true is found.ĮditorConfig files are read top to bottom and the most recent rules found take precedence. editorconfig in the directory of the opened file and in every parent directory. When opening a file, EditorConfig plugins look for a file named. indent_style = space indent_size = 2Ĭheck the Wiki for some real-world examples of projects using EditorConfig files. end_of_line = lf insert_final_newline = true # Matches multiple files with brace expansion notation Root = true # Unix-style newlines with a newline ending every file
0 kommentar(er)
