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

sublimelint

by lunixbochs ALL Top 100

Error highlighting in Sublime Text.

Labels linting

Details

  • 2015.10.10.07.11.17
    2013.01.19.22.38.15
  • github.​com
  • 9 years ago
  • 48 minutes ago
  • 13 years ago

Installs

  • Total 250K
  • Win 143K
  • Mac 64K
  • Linux 43K
Dec 14 Dec 13 Dec 12 Dec 11 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
Windows 0 4 5 9 7 8 3 8 3 6 7 2 5 4 2 5 2 0 0 0 0 3 7 11 2 9 4 6 3 7 0 0 2 5 4 6 5 6 2 4 5 6 1 6 3 8
Mac 0 0 1 1 1 3 0 1 0 3 2 1 1 1 0 2 0 0 0 0 0 1 0 1 1 1 0 0 0 2 0 0 1 2 1 2 1 2 2 1 2 0 2 1 1 1
Linux 0 0 1 5 2 3 0 1 1 0 2 2 3 1 0 2 0 0 0 0 0 1 1 0 1 0 3 2 3 2 0 0 2 5 2 0 0 2 1 3 1 0 1 3 1 3

Readme

Source
raw.​githubusercontent.​com

Sublime Lint

A framework for error highlighting in the Sublime Text editor.

It's easy to add language support. Take a look at the linter repository for examples.

Linters in your Sublime Text User/linters folder will be automatically used. Changes to linters in this folder will be overwritten on automatic update. If you want to change a builtin linter, disable it in the Sublime Lint preferences and copy the source to a new file/class name.

You can also import Linter and subclass it inside plugin_loaded() from any other Sublime plugin.

Installation

You can install in ST3 by adding this repository to Package Control, which does automatic updates.

Alternatively, you can clone sublimelint into your Packages folder and switch to the st3 branch manually, but you will need to update manually.

Usage

Make sure you have the necessary command installed to lint your language - there's a list in the linter repository README.

It will lint as you edit any file in a supported language. Check the status bar for messages, and take a look at the SublimeLint commands in the Command Palette.

There's a current bug that makes it sometimes take a few seconds to start linting upon an editor restart. Be patient.

Command Palette

Press cmd+shift+p on OS X, ctrl+shift+p for everyone else. Type sublimelint to see the available commands:

  • Next Error - Jump to the next highlighed error or warning in your code.
  • Previous Error - Jump to the previous error.
  • Show All Errors - Open a command panel listing all errors in the current file.
  • Report (Open Files) - Lint all open files and show a report in a new view.
  • Preferences: SublimeLint Settings - User - Change global and linter settings.

Settings

You can change a few useful per-language settings by opening “SublimeLint Settings - User” via the Command Palette. Some languages (like C and C++) have additional linter-specific settings.

Example language settings:

"Ruby": {
    // This command is run against your code.
    // Some linters use a temporary file, while others pipe code to stdin.
    "cmd": ["ruby", "-wc"],
    // Disable the linter.
    "disable": false,
    // Exclude file patterns from being linted.
    "excludes": ["Rakefile", "*.blah"]
}