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 708
  • Linux 634
May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14 May 13 May 12 May 11 May 10 May 9 May 8 May 7 May 6 May 5 May 4 May 3 May 2 May 1 Apr 30 Apr 29 Apr 28 Apr 27 Apr 26 Apr 25 Apr 24 Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12
Windows 2 1 1 1 1 2 0 0 2 1 0 1 3 0 1 2 3 1 1 1 0 0 1 0 1 0 2 0 1 1 1 1 0 0 1 2 1 2 4 2 1 1 1 1 6 4
OS X 1 1 0 0 0 0 0 0 1 1 0 1 0 0 0 0 1 0 2 0 2 0 1 1 1 1 1 0 1 0 0 0 0 2 0 0 1 1 2 0 0 1 0 0 2 0
Linux 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 1 2 0 1 0 0 0 0 3 0 0 0 0 0 3 3 1 0 0 0 1 0 0 1 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Build Next

Build Status

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.