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 2K
  • Win 1K
  • OS X 618
  • Linux 575
Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23 Dec 22 Dec 21 Dec 20 Dec 19 Dec 18 Dec 17 Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11 Dec 10 Dec 9 Dec 8 Dec 7 Dec 6
Windows 2 1 1 3 0 2 0 0 1 0 2 1 2 1 0 4 1 2 1 1 2 6 2 1 2 1 0 1 3 1 2 0 1 1 1 2 0 1 1 2 3 1 3 2 2
OS X 1 0 1 2 1 0 2 1 1 4 2 0 0 2 1 2 1 1 0 1 1 0 2 0 0 0 0 0 4 1 0 1 2 2 0 0 0 1 0 0 0 1 2 0 1
Linux 1 5 1 1 0 1 1 0 1 1 0 0 1 0 1 0 2 0 0 0 0 1 1 0 1 0 0 1 1 2 1 0 1 0 0 0 0 0 2 0 0 0 0 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.