EditorConfig helps developers maintain consistent coding styles between different editors
Support this project & level up your Sublime skills with this excellent Sublime Power User course by Wes Bos
EditorConfig with Package Control and restart Sublime.
See the EditorConfig site for documentation.
Explanation of the properties can be found on the EditorConfig site.
My recommended default settings
# editorconfig.org root = true [*] indent_style = tab end_of_line = lf charset = utf-8 trim_trailing_whitespace = true insert_final_newline = true [*.md] trim_trailing_whitespace = false
If you can't remember all settings managed by the EditorConfig file, you'll love the
editorconfig + tab, and your editor will focus on the first setting's value (indent_style = lf). You can change the value, if you want, and jump to the next setting's value by hitting tab and so on. Settings are somewhat autocompleted, and if you don't remember all possible values, simply remove the setting value to see them all as a comment.
You can be in a context where
editorconfig + tab trigger another snippet. In that case, simply use
Goto anywhere (Ctrl + P on Linux/Windows or ⌘ + P on macOS), type
Snippet: editorconfig and hit Enter.
View active config
The active config is printed in the Sublime console.
Even though there is a
trim_trailing_whitespace property. I would still recommend you set
"draw_white_space": "all" and/or
"trim_trailing_white_space_on_save": true in your Sublime preferences to prevent you from accidentally committing whitespace garbage whenever a project is missing a .editorconfig file.
This plugin does its changes transparently in the background. I would recommend the excellent Modific plugin if you would like to see what changed.
MIT © Sindre Sorhus