sublimelint
Error highlighting in Sublime Text.
Details
Installs
- Total 246K
- Win 141K
- Mac 64K
- Linux 42K
Sep 30 | Sep 29 | Sep 28 | Sep 27 | Sep 26 | Sep 25 | Sep 24 | Sep 23 | Sep 22 | Sep 21 | Sep 20 | Sep 19 | Sep 18 | Sep 17 | Sep 16 | Sep 15 | Sep 14 | Sep 13 | Sep 12 | Sep 11 | Sep 10 | Sep 9 | Sep 8 | Sep 7 | Sep 6 | Sep 5 | Sep 4 | Sep 3 | Sep 2 | Sep 1 | Aug 31 | Aug 30 | Aug 29 | Aug 28 | Aug 27 | Aug 26 | Aug 25 | Aug 24 | Aug 23 | Aug 22 | Aug 21 | Aug 20 | Aug 19 | Aug 18 | Aug 17 | Aug 16 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 6 | 9 | 12 | 11 | 16 | 14 | 4 | 10 | 6 | 9 | 7 | 5 | 13 | 7 | 5 | 8 | 7 | 8 | 12 | 5 | 3 | 11 | 7 | 5 | 10 | 10 | 2 | 4 | 10 | 10 | 6 | 5 | 14 | 11 | 11 | 7 | 8 | 6 | 8 | 15 | 9 | 7 | 11 | 3 | 13 | 5 |
Mac | 1 | 4 | 2 | 2 | 4 | 1 | 0 | 1 | 2 | 1 | 2 | 2 | 1 | 2 | 1 | 3 | 2 | 3 | 2 | 6 | 1 | 1 | 2 | 2 | 5 | 3 | 3 | 2 | 2 | 2 | 1 | 0 | 2 | 0 | 2 | 2 | 3 | 6 | 4 | 1 | 2 | 2 | 1 | 2 | 1 | 2 |
Linux | 0 | 1 | 1 | 2 | 1 | 3 | 2 | 3 | 1 | 2 | 2 | 1 | 1 | 0 | 2 | 1 | 1 | 3 | 2 | 2 | 1 | 0 | 2 | 5 | 1 | 2 | 2 | 1 | 1 | 2 | 3 | 1 | 2 | 1 | 3 | 2 | 2 | 5 | 2 | 4 | 3 | 0 | 1 | 2 | 3 | 2 |
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"]
}