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

Sublime​On​Save​Build

by alexnj ALL

Trigger a build the moment you save a file in Sublime Text 2. Works best with web projects that make use of Less, Compass and any other pre-processor or a makefile.

Details

  • 2016.08.05.17.17.02
  • github.​com
  • github.​com
  • 8 years ago
  • 2 hours ago
  • 13 years ago

Installs

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

Readme

Source
raw.​githubusercontent.​com

SublimeOnSaveBuild Sublime Plugin

This is a simple plugin for Sublime Text 2 to trigger a build on each save.

Not all projects might need this plugin, especially if the build operation is lengthy. However, if you have a build that does things like pre-processing CSS via tools like LessCSS and stitching all JS files together, this might be very handy.

Installation

With the Package Control plugin: The easiest way to install SublimeOnSaveBuild is through Package Control, which can be found at this site: http://wbond.net/sublime_packages/package_control

Once you install Package Control, restart ST2 and bring up the Command Palette (Command+Shift+P on OS X, Control+Shift+P on Linux/Windows). Select “Package Control: Install Package”, wait while Package Control fetches the latest package list, then select SublimeOnSaveBuild when the list appears. The advantage of using this method is that Package Control will automatically keep SublimeOnSaveBuild up to date with the latest version.

Without Git: Download the latest source from GitHub and copy the SublimeOnSaveBuild folder to your Sublime Text 2 “Packages” directory.

With Git: Clone the repository in your Sublime Text 2 “Packages” directory:

git clone git://github.com/alexnj/SublimeOnSaveBuild.git

The “Packages” directory is located at:

  • OS X:

    ~/Library/Application Support/Sublime Text 2/Packages/

  • Linux:

    ~/.config/sublime-text-2/Packages/

  • Windows:

    %APPDATA%/Sublime Text 2/Packages/

Configuring

There are a number of configuration options available to customize the behavior of SublimeOnSaveBuild. For the latest information on what options are available, select the menu item Preferences->Package Settings->SublimeOnSaveBuild->Settings - Default.

Do NOT edit the default SublimeOnSaveBuild settings. Your changes will be lost when SublimeOnSaveBuild is updated. ALWAYS edit the user SublimeOnSaveBuild settings by selecting Preferences->Package Settings->SublimeOnSaveBuild->Settings - User.

  • build_on_save Set to 1 to trigger a build on save. By default, this is set to 1. I.e., SublimeOnSaveBuild attempts to build all projects. You can change this behavior and build only specific projects by configuring the user specific setting of build_on_save to 0 and project specific setting to 1.

  • filename_filter SublimeOnSaveBuild matches the name of the file being saved against this regular expression to determine if a build should be triggered. By default, the setting has a value of "\\.(css|js|sass|less|scss)$".

Usage

  1. Make sure you have a build operation set up in your Sublime Text 2 project and you are able to build using Control+B (Linux/Windows) or Command+B (OS X).
  2. Hit your favorite shortcut to Saveit should trigger a build.

Good luck!