CODEWITHSUNDEEP
textthemessublimetext3editorsidebar
GinTonic
GinTonic

Reputation: 1000

Theme for text files in Sublime Text 3

Since one of the last updates the theme for .txt files in my Sublime Text 3 has changed. I am currently using the Monokai Theme for Sublime and would like to have the same theme options for all file types (black background, line numbers on the left, slim right sidebar/margin). Only when opening .txt files the background switches to white and the sidebars/margins become too wide taking half of the screen space.

An example can be seen on the left side of the screenshot. on the right side my sublime settings are displayed: enter image description here

I have tried changing the "Preferences" -> "Color Scheme... " to any other color scheme. The changes seem to apply to the other file types I use (.json, .csv, .py etc). Only the .txt files seem not to be affected by any scheme changes.

Changing "Preferences" -> "Theme..." doesn't change much.

Neither could I find any specific settings for .txt files in "Preferences" -> "Settings".

Upvotes: 0

Views: 833

Answers (1)

MattDMo
MattDMo

Reputation: 102852

There are two potential sources of the problem - an overzealous plugin or a messed-up .sublime-settings file. First, look in your Packages/User directory, where Packages is the one opened when selecting Preferences → Browse Packages…:

  • Linux: ~/.config/sublime-text-3/Packages
  • OS X: ~/Library/Application Support/Sublime Text 3/Packages
  • Windows Regular Install: C:\Users\YourUserName\AppData\Roaming\Sublime Text 3\Packages
  • Windows Portable Install: InstallationFolder\Sublime Text 3\Data\Packages

In the User directory, look for files named Text.sublime-settings or Markdown*.sublime-settings, then try deleting them (or renaming them to *.bak so they won't get processed).

If that doesn't work, take the list of all installed plugins from Packages/User/Package Control.sublime-settings and put it in your user preferences in the "ignored_packages" setting. Hopefully that will solve the problem. To identify the offending plugin, start removing plugins from "ignored_packages" one at a time until the behavior comes back.

Upvotes: 2

Related Questions