This reason prevented me from using the sublime merge.īy the way, from today I am going to use sublime text instead of gedit when I need to do small text edits. I hope that switching to a dark theme was free because it is such a basic feature.I have already given my feedback, expressing my disappointment with the dark theme being a premium feature. In each of those, put the following content: Packages/User/File Mode - Merge.sublime-settings.Packages/User/Diff - Merge.sublime-settings.Packages/User/Commit Message - Merge.sublime-settings.Thus if you are using the theme 'Merge', you should create files: This way your customizations will be retained upon program updates.

Based on how Sublime products load settings, you'll want to create User versions of each of those three files. You can customize all three to use the same color scheme, or use different color schemes for each. In each of those files is a setting named 'color_scheme'. File Mode - Merge Dark.sublime-settings.Commit Message - Merge Dark.sublime-settings.If you are using the theme 'Merge Dark', the files will be: Commit Message - Merge.sublime-settings.So, if you are using the theme 'Merge', the files will be named: Beyond that, each theme has it's own version of the settings file for each editor control. Since Sublime Merge is more complex than Sublime Text in its interface, there are actually a few different places that color schemes are used:Įach of these has a settings file that controls the editor control used. However, I don't believe every scope will be auto-generated, so the example at the end of this comment may be of use. Before then, each color scheme would need to be customized. This is because new builds will automatically generate some necessary scope rules for the inserted and deleted regions of the diff view. This is going to work best for builds 1105 and newer. Here is some info on how to customize the color scheme used in Sublime Merge.

Sublime merge editor