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

  • 1.0.5
  • github.​com
  • github.​com
  • 2 months ago
  • 12 minutes ago
  • 6 months ago

Installs

  • Total 5K
  • Win 2K
  • OS X 2K
  • Linux 901
Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10
Windows 15 17 30 22 16 25 25 37 45 37 41 36 13 11 16 22 17 26 18 7 22 28 23 22 8 27 8 14 22 25 23 26 12 8 14 14 25 18 19 20 21 12 14 17 21 14
OS X 12 15 26 16 7 13 15 21 30 27 18 22 9 13 11 18 14 18 19 11 14 13 16 14 18 15 10 11 28 22 24 23 15 13 5 20 19 20 18 21 6 12 18 19 15 14
Linux 8 13 5 12 14 5 9 11 13 16 10 12 10 13 10 5 4 11 8 5 11 6 2 8 10 7 7 6 13 6 11 8 13 7 8 10 9 5 7 8 4 7 6 7 10 3

Readme

Source
raw.​githubusercontent.​com

Skins

Package Control

With Skins users can change the theme and colour scheme of Sublime Text together with only one command. A skin is nothing else but a collection of settings applied to Sublime Text, if a skin is selected. Skins can be provided in theme packages such as Boxy Theme or they can be created by users themselves by saving the current settings as a User Skin of any name.

scr

End Users

General Usage

Open the command panel with Ctrl+Shift+P and type Select Skin, Save User Skin or Delete User Skin.

Windows / Linux

Use Ctrl+F12 to quickly open the Select Skin panel

OS X

Use Super+F12 to quickly open the Select Skin panel

Settings

By default only color_scheme, theme, font_face and font_size are stored by Save User Skin. If you want more settings to be stored, you can change the skin-template in the Skins.sublime-settings.

Example

"skin-template":
{
    "Preferences": ["color_scheme","theme","font_face","font_size" /* ... */ ],
    "SublimeLinter": {
        /* structured settings are supported, too */
        "user": ["error_color","gutter_theme","warning_color"]
    }
    /* add more packages here */
}

Theme Developers

General

Skins parses all <AnyName>.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 a <NodeName>.sublime-settings file with all settings to write to. Therefore settings can be provided not only for Sublime Text but for any installed package such as SublimeLinter, too. A skin must at least contain the Preferneces node with color_scheme and theme settings to be valid but can 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 Skin
"command": "set_skin",
"args": { "package": "Skins", "name": "Monokai" }
Save User Skin

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 User Skin

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