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 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,įITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.Root = true # Unix-style newlines with a newline ending every file THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR The above copyright notice and this permission notice shall be included inĪll copies or substantial portions of the Software. To use, copy, modify, merge, publish, distribute, sublicense, and/or sellĬopies of the Software, and to permit persons to whom the Software isįurnished to do so, subject to the following conditions: In the Software without restriction, including without limitation the rights Of this software and associated documentation files (the “Software”), to deal Support this project via gittip or paypal.Īll files in this package is licensed under the MIT license.Ĭopyright © 2013 Chris is hereby granted, free of charge, to any person obtaining a copy Windows: %APPDATA%/Sublime Text 3/Packages/Sublime Text 3 Snippets.Mac: ~/Library/Application Support/Sublime Text 3/Packages/Sublime Text 3 Snippets.Linux: ~/.config/sublime-text-3/Packages/Sublime Text 3 Snippets. Save files to the Packages/Sublime Text 3 Snippets directory, then relaunch Sublime:.Select Sublime Text 3 Snippets to install.Select Package Control: Install Package.Bring up the Command Palette (Command+Shift+P on OS X, Control+Shift+P on Linux/Windows).A full list the api of Sublime Text 3 is available on the official page. A sublime plugin complete with Sublime Text 3 snippets, helps you to create your own plugin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |