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

sublime-text-2-buildview

by rctay ST2/ST3

A Sublime Text 2/3 plugin to show build output in a view.

Details

  • 2018.04.15.11.41.56
  • github.​com
  • github.​com
  • 8 months ago
  • 2 hours ago
  • 6 years ago

Installs

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

Readme

Source
raw.​githubusercontent.​com

A Sublime Text 2/3 plugin to show build output in a view.

Gratipay me! Donate with Bitcoin Donate with Ethereum

In Sublime Text, build results are shown in a fixed horizontal panel; you can't drag it to put it vertically next to your code, like in Eclipse, VS.

With this plugin, like any other view, you can put your build results where you want:

This is super useful if you are repeatedly running a program on your code/ script and want to have its output handy. (You probably already have a .sublime-build or build_systems entry in your .sublime-project.)

The core functionality is done in pipe_views.PipeViews, an abstraction allowing Unix-like “pipes” to be created between Views in Sublime.

Usage

The plugin hooks on to the keyboard shortcuts for launching builds; if you have different shortcuts for them, change the .sublime-keymap files accordingly. These bindings must have the following context:

"context": [{"key": "build_fake", "operator":"equal", "operand":true}]

Several aspects of the plugin's behaviour can be changed as detailed below. They can be changed on a per-view basis via the Command Palette in either the view source code or with build output, or through settings under "buildview".

Note: it seems settings set via Command Palette are persisted through sublime exits/launches.

Disabling

Command Palette: - Disable/Enable buildview for this window

key: "buildview.enabled" values: true/false

Sublime's settings hierarchy is respected. So you could, for example, enable the plugin only for selected projects, by setting "enabled" to false in Packages/User/Preferences.sublime-settings, and set it to true in your .sublime-project.

For example, you can add this to your Preferences.sublime-settings:

{
    ...
    "buildview.enabled": false
    ...
}

Then in the project's .sublime-project file:

{
    ...
    "folders": [...]
    "settings": {
        "buildview.enabled": true,
        "buildview.scroll": "top"
    }
    ...
}

("scroll" added for demonstration; for details on "scroll", refer below.)

Output scrolling

Command Palette: - Build output always at top - Build output always at end - Build output stays at same position

key: "buildview.scroll"

values: - "top" - "bottom" - "last"

default: "bottom"

The plugin can scroll the output to the top, bottom, or the position before the current build was launched. The default is to scroll to the bottom (ie. continually show fresh output as it is emitted).

“Save changes?” warning

key: "buildview.silence_modified_warning"

values: true/false

default: true.

Since version 90e2365182e9566b2fa79dd7dc79d6b0d7e433f6 (Package Control: 2014.01.27.15.16.48), closing the build output view, directly, or indirectly, eg. by exiting Sublime Text, no longer causes a “Save changes?” warning to be displayed.

If you wish to have the old behaviour (of having a warning displayed), set to false.

Suppress build results panel

The built-in build results view will display momentarily. To disable this, use the User preference setting:

{
    ...
    "show_panel_on_build": false,
    ...
}

Known Issues/TODO

  • pin/unpin location, so that subsequent builds scrolls to the same location
  • build view is “forgotten” after restarting Sublime
  • improve disabling/enabling options (eg whitelists, blacklists)
  • improve namespacing of settings into a dictionary, once sublime supports merging of settings dictionaries through the hierarchy. For example, if buildview hypothetically read settings from a dictionary, and you had in your Preferences.sublime-settings

    { … “buildview”: { “enabled”: false, “scroll”: “top” } … }

and you then did this in the project's .sublime-project file

{
       ...
       "folders": [...]
       "settings": {
           "buildview": {
               "enabled": true
           }
       }
       ...
   }

buildview would behave as though the `"scroll"` setting was not defined
because sublime does not automatically merge settings dictionaries through
the settings hierarchy, so the `"scroll"` setting does not bubble up.

Pull requests welcome!

Hacking notes

  • after editing pipe_views.py, restart Sublime or re-save commands.py for the changes to take effect.
  • who's view is it anyway? A variety of names are used for views in the source code, according to their different roles:
    • source view: the built-in view that shows up when you click Show Build Results
    • destination view: the view that mirrors the build output, the one with the title “Build Output”
    • otherwise, a view should generally refer to one holding the source for the build

Donate

If you liked this plugin, you can donate here:
Gratipay me! Donate with Bitcoin Donate with Ethereum