![]() Makes auto indent a little smarter, e.g., by indenting the next line Calculates indentation automatically when pressing enter Set to false to disable detection of tabs vs. backspace insert/delete up to the next tabstop If translate_tabs_to_spaces is true, use_tab_stops will make tab and Set to true to insert spaces when tab is pressed The number of spaces a tab is considered equal to Set to true to turn spell checking on by default Columns in which to display vertical rulers Hides the fold buttons unless the mouse is over the gutter Fold buttons are the triangles shown in the gutter to fold regions of text Spacing between the gutter and the text Set to false to hide the gutter altogether "word_separators": Set to false to prevent line numbers being drawn in the gutter ![]() Characters that are considered to separate words "subpixel_antialias" and "no_round" (OS X only) Valid options are "no_bold", "no_italic", "no_antialias", "gray_antialias", Because of this, setting them here will have no effect: you must set them specific settings file, for example, "Preferences (Linux).sublime-settings". “color_scheme”: “Packages/Color Scheme - Default/Monokai.tmTheme”, // Note that the font_face and font_size are overriden in the platform Sets the colors used within the text area example, in Packages/Python/Python.sublime-settings for python files. Settings may also be placed in file type specific options files, for “User/Preferences.sublime-settings”, which overrides the settings in here. While you can edit this file, it’s best to put your changes in I’ll include here a copy of my default Preferences.sublime-settings (which is the one I’ve modified) in case there’s a conflict with another of the options. This is of course my fault for not using version control (though you can be sure that’s never a pitfall I’ll ever fall for again), but still, I should have been told initially that my files didn’t load, or perhaps a version could be kept in Sublime’s collective memory, a la Notepad++, or something to that effect. I’m sorry to say that I lost a ~300 line python script I’ve worked on all week as well as the files it was meant to process and export. However, the file has now been wiped to 0 bytes, reflecting the actual blank file in Sublime’s display. ![]() ![]() Again, there is no indication that anything wrong has happened. A popup will appear, stating the files have changed, would you like to reload this file or cancel? regardless of whichever option you choose, Sublime will attempt to load the file, fail to do so, and then show the blank file once more. If you look at the applicable files in Nautilus (or the file system viewer of your choice) you will see that the file still exists and the data is still intact.ħ- Give those same files focus within Sublime. These files will show as blank in the editor but there will otherwise be no indication that anything is wrong or that the files failed to load.Ħ- Mount the drive. This is using an NTFS-formatted file system, btw, have not tested with ext3/4.ġ- Make sure “remember_open_files”: true, in the active settingsģ- Close Sublime, thus saving session dataĤ- Unmount the drive (which I did initially via restarting, but manual unmounting also delivers)ĥ- Open Sublime, restoring the session, including files that cannot be opened on the unmounted drive. My experience with the program has unfortunately been marred by an unfortunate data loss bug, which I have been able to reproduce exactly and have caused crashes while attempting, so hopefully this is helpful: For a bit of background, I’m on a Linux Mint 13 圆4 system and just barely installed sublime (a fantastic feature set, btw, I’m very impressed). ![]()
0 Comments
Leave a Reply. |