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
  • 5 years ago
  • 3 hours ago
  • 9 years ago

Installs

  • Total 229K
  • Win 129K
  • Mac 60K
  • Linux 39K
Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 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
Windows 14 30 19 18 23 13 23 22 23 25 19 14 16 18 32 19 18 8 18 27 25 23 18 12 17 16 17 19 20 17 13 14 19 12 15 20 25 19 21 12 15 24 19 30 21 10
Mac 6 4 6 7 4 6 7 4 6 4 1 5 2 5 5 11 12 5 3 8 8 2 6 4 1 0 3 3 2 5 4 8 2 1 4 4 8 6 3 7 7 2 3 4 7 2
Linux 3 2 5 5 3 3 4 4 7 5 5 4 7 4 11 6 3 6 4 5 6 3 5 3 3 2 2 4 8 8 3 6 4 1 2 3 3 4 5 2 6 1 3 7 3 4

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"]
}