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

Build Next

Sublime Text plugin to improve build system

Labels build system

Details

Installs

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

Readme

Source
raw.​githubusercontent.​com

Build Next

Build Next is a Sublime Text plugin to improve the default build system.

Features

  • Extend Default.exec plugin and no external dependencies.
  • Zero user preferences and preferences per build system.
  • Close build results view if there are not errors.
  • Show a dot icon in the gutter area close to the error.
  • Draw an horizontal region close to the column (tabs-aware) of the error.
  • Open finally the output panel.
  • Go to the results following a line number order.
  • Wrap around the end of the document for the next (previous) result.
  • The output panel content is refreshed on the next (previous) result command.

Requirements

At least Sublime Text 3 Build 3124.

Installation

After installing the plugin with Sublime Package Manager, you should add the following user key bindings (Preferences / Key Bindings - User) to engage it:

[
...
    { "keys": ["f4"], "command": "goto_next_error" },
    { "keys": ["shift+f4"], "command": "goto_prev_error" },
...
]

This configuration overrides the default key bindings next_result and prev_result.

Preferences

There are not user preferences, but there are preferences per build system file. The preferences are embedded in the build file, contained in the env property.

There are use cases where the following preferences are useful, like displaying the output after the unit test command or adjusting the error column, because the build command is zero based column.

  • ST_BUILD_SHOW_OUTPUTVIEW (default false): to display always the Build Results panel, even if there are not error and the build command exit code is zero.

  • ST_BUILD_ADJUST_COLUMNERROR (default 0): to adjust the column of the error adding a value.

For instance,

...
    "env":
    {
        "ST_BUILD_SHOW_OUTPUTVIEW": "true"
    }
...
  • ST_BUILD_PUT_PRIORITY (default “”): to put priority on errors containing a token.

Notes

The build system should contain the file_regex property for the filename, line, column and message field. For instance, a JSHint build setting (JSHint.sublime-build):

{
    "selector": "source.js, source.json",

    "cmd": ["jshint", "$file"],
    "shell": true,

    "file_regex": "^(.*): line (\\d+), col (\\d+), (.+)$",

    "windows":
    {
        "cmd": ["jshint.cmd", "$file"]
    }
}

I recommend SublimeOnSaveBuild plugin, if you need to execute the build when you save the file.