ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Skins

by deathaxe ST3

Easily switch theme and color scheme of Sublime Text with only one command.

Labels themes, utilities

Details

Installs

  • Total 12K
  • Win 5K
  • OS X 4K
  • Linux 2K
Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8 Sep 7 Sep 6 Sep 5 Sep 4 Sep 3 Sep 2 Sep 1 Aug 31 Aug 30 Aug 29 Aug 28 Aug 27 Aug 26 Aug 25 Aug 24 Aug 23 Aug 22 Aug 21 Aug 20 Aug 19 Aug 18 Aug 17 Aug 16 Aug 15 Aug 14 Aug 13 Aug 12
Windows 8 15 12 8 10 13 17 17 8 7 12 19 43 24 23 10 15 15 19 19 14 14 19 10 12 14 18 24 8 22 15 17 22 19 16 21 20 7 11 20 21 21 19 11 12 13
OS X 10 7 8 6 9 10 4 9 17 6 13 19 30 29 7 10 3 7 9 14 9 10 11 5 9 15 12 13 8 11 11 6 13 14 15 14 8 7 6 18 10 11 12 17 13 7
Linux 1 6 5 5 4 2 3 8 7 4 7 6 10 6 7 5 4 10 7 6 6 6 5 2 11 5 7 3 11 9 4 8 9 10 7 11 9 5 9 10 10 10 8 13 7 3

Readme

Source
raw.​githubusercontent.​com

Skins

License Package Control

Skins gives users the ability to change their current Sublime Text color scheme and theme with a single command. When a skin is selected, a certain set of settings is applied to Sublime Text. Skins can be provided in theme packages such as Boxy Theme or they can be created by users themselves by saving the current settings to a new User Skin.

screenshot

End Users

General Usage

  1. Open the Command Palette
  2. Type one of the following three commands:
    • UI: Select Skin
    • UI: Save Skin
    • UI: Delete Skin.
Keyboard shortcuts

To quickly open the UI: Select Skin menu use:

  • Ctrl+F12 on Windows / Linux
  • Super+F12 on macOS

Settings

By default the following settings are stored by Save User Skin

  • color_scheme
  • theme
  • font_face
  • font_size

To edit the settings

  1. Open the Command Palette
  2. Type Preferences: Skins Settings

The settings are stored in Packages/User/Skins.sublime-settings.

Example

"skin-template":
{
    // List of settings to load from / save to Preferences.sublime-settings
    "Preferences":
    [
        "color_scheme",
        "theme",
        "font_face",
        "font_size"
    ],
    // List of settings to load from / save to SublimeLinter.sublime-settings
    "SublimeLinter":
    {
        "user":
        [
            "error_color",
            "gutter_theme",
            "warning_color"
        ]
    }
}

Theme Developers

General

Skins parses all *.skins files in all packages. They are expected to store a collection of settings for sublime text and other packages. More than one skins file can exist in a package. The name of the file does not matter, but the names of the skins inside must be unique per package. The quick panel will show these names. The Package providing it is displayed in the second row as a kind of description.

File Format

{
    // skin
    "Boxy Tomorrow (Green)": {
        // Packages/User/Preferences.sublime-settings
        "Preferences": {
            "color_scheme": "Packages/Boxy Theme/schemes/Boxy Tomorrow.tmTheme",
            "theme": "Boxy Tomorrow.sublime-theme",
            "theme_accent_green" : true,
            "theme_accent_orange": null,
            "theme_accent_purple": null
        },
        // Packages/User/SublimeLinter.sublime-settings
        "SublimeLinter": {
            "user": {
                // ...
            }
        }
    },

    // skin
    "Monokai 2": {
        // ...
    },

    // ...
}

Each child node of a skin represents the settings to be written to a Packages/User/*.sublime-settings file. Therefore settings can be provided not only for Sublime Text but for any installed package such as SublimeLinter. A skin must at least contain the Preferences node with color_scheme or theme settings to be valid but may include any other setting accepted by Sublime Text.

Settings with null value, are deleted in the sublime-settings files.

Commands

Skins exports the following commands to directly interact with all available skins. They can be used to create key bindings or command shortcuts to the most frequent used skins.

Set Skins

To open a quick panel with all available skins call:

"command": "set_skin"
"args": { }

To open a quick panel with all skins provided by a single package call:

"command": "set_skin",
"args": { "package": "Skins" }

To directly apply a certain predefined skin call:

"command": "set_skin",
"args": { "package": "Skins", "name": "Monokai" }

To apply a saved user skin call:

"command": "set_skin",
"args": { "package": "User", "name": "Preset 01" }
Save Skins

The following example will directly save the current look and feel as Preset 01 in the Packages/User/Saved Skins.skins file.

"command": "save_user_skin",
"args": { "name": "Preset 01" }
Delete Skins

The following example will directly delete Preset 01 from the Packages/User/Saved Skins.skins file.

"command": "delete_user_skin",
"args": { "name": "Preset 01" }

Inspired by