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
  • 6 years ago
  • 2 hours ago
  • 10 years ago

Installs

  • Total 233K
  • Win 132K
  • Mac 61K
  • Linux 40K
Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 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
Windows 0 26 21 31 18 17 17 20 16 29 16 18 15 10 28 25 20 14 28 23 24 24 24 20 24 23 18 15 26 27 30 20 27 12 13 22 17 24 15 10 15 14 15 13 19 18
Mac 0 4 2 6 10 3 8 3 4 7 5 6 3 3 6 5 6 4 4 5 4 5 9 7 13 2 4 3 8 12 8 6 10 3 4 11 5 5 6 3 2 0 3 3 5 2
Linux 0 5 7 7 4 1 2 0 7 14 2 9 4 3 3 3 3 4 2 1 4 6 6 6 5 7 2 7 7 5 9 5 3 8 7 7 3 2 6 3 4 2 4 6 3 5

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