The wiki has a complete list of properties. Note that not all properties are supported by every plugin. Special characters can be escaped with a backslash so they won't be interpreted as wildcard patterns. Matches any integer numbers between num1 and num2, where num1 and num2 can be either positive or negative Matches any of the strings given (separated by commas) ( Available since EditorConfig Core 0.11.0) Matches any string of characters, except path separators ( /) 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 Because the star is inside the square brackets, it loses its usual meaning of zero or more characters and becomes a literal *.Root = true # Unix-style newlines with a newline ending every file expands to a file name that consists of a dot immediately followed by one of the characters f, *, or u (and nothing else after that). As a special case, the above does not match files that start with a dot because such files are, by convention, "hidden." Normally, * means zero or more of any character. In other words, this glob requires that both f and u be present in the filename and that they appear in the order f then u. *.*f*u expands to a file name that contains a dot followed (not necessarily immediately) by an f and ends with a u. If you don't want to see them, and one usually doesn't, then omit the first glob and use simply: ls -lL *.** The hidden files generally serve as configuration files for various programs. The second, *.**, expands to files that have a dot somewhere in the name but do not begin with dot. **, expands to files that start with a dot (which means that they are normally 'hidden'). To also insist that the f or u be preceded by a dot, try: ls -lL. This looks for files in the data directory that contain a dot followed by f or u but not ending in f or u: ls -lL datafiles/*.**
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |