sublime text settings
Last active
December 25, 2015 05:39
-
-
Save jfreels/6925909 to your computer and use it in GitHub Desktop.
Sublime Text user settings
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
// Sets the colors used within the text area | |
"color_scheme": "Packages/Color Scheme - Default/Monokai.tmTheme", | |
// Note that the font_face and font_size are overriden in the platform | |
// specific settings file, for example, "Preferences (Linux).sublime-settings". | |
// Because of this, setting them here will have no effect: you must set them | |
// in your User File Preferences. | |
"font_face": "Consolas", | |
"font_size": 13, | |
// The number of spaces a tab is considered equal to | |
"tab-size": 2, | |
// Set to true to insert spaces when tab is pressed | |
"translate_tabs_to_spaces": false, | |
// Calculates indentation automatically when pressing enter | |
"auto_indent": true, | |
// Makes auto indent a little smarter, e.g., by indenting the next line | |
// after an if statement in C. Requires auto_indent to be enabled. | |
"smart_indent": false, | |
// By default, auto complete will commit the current completion on enter. | |
// This setting can be used to make it complete on tab instead. | |
// Completing on tab is generally a superior option, as it removes | |
// ambiguity between committing the completion and inserting a newline. | |
"auto_complete_commit_on_tab": false, | |
// By default, shift+tab will only unindent if the selection spans | |
// multiple lines. When pressing shift+tab at other times, it'll insert a | |
// tab character - this allows tabs to be inserted when tab_completion is | |
// enabled. Set this to true to make shift+tab always unindent, instead of | |
// inserting tabs. | |
"shift_tab_unindent": true, | |
"detect_indentation": false | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment