sublimelint
Error highlighting in Sublime Text.
Details
Installs
- Total 250K
- Win 144K
- Mac 64K
- Linux 43K
| Feb 18 | Feb 17 | Feb 16 | Feb 15 | Feb 14 | Feb 13 | Feb 12 | Feb 11 | Feb 10 | Feb 9 | Feb 8 | Feb 7 | Feb 6 | Feb 5 | Feb 4 | Feb 3 | Feb 2 | Feb 1 | Jan 31 | Jan 30 | Jan 29 | Jan 28 | 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 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 2 | 6 | 3 | 6 | 3 | 4 | 6 | 2 | 5 | 0 | 4 | 4 | 5 | 3 | 4 | 4 | 4 | 5 | 3 | 3 | 5 | 3 | 6 | 2 | 3 | 3 | 9 | 4 | 5 | 5 | 1 | 6 | 2 | 2 | 4 | 6 | 3 | 3 | 3 | 3 | 5 | 10 | 2 | 19 | 3 | 6 |
| Mac | 0 | 2 | 0 | 0 | 2 | 1 | 0 | 2 | 3 | 1 | 3 | 1 | 1 | 1 | 2 | 1 | 0 | 1 | 1 | 4 | 2 | 2 | 0 | 1 | 0 | 1 | 2 | 4 | 0 | 2 | 0 | 2 | 3 | 0 | 1 | 4 | 0 | 1 | 1 | 0 | 3 | 0 | 1 | 2 | 0 | 0 |
| Linux | 0 | 3 | 1 | 0 | 2 | 3 | 0 | 2 | 1 | 1 | 0 | 1 | 5 | 0 | 0 | 3 | 2 | 3 | 1 | 1 | 2 | 3 | 2 | 0 | 0 | 1 | 1 | 6 | 4 | 4 | 0 | 1 | 2 | 1 | 2 | 1 | 4 | 2 | 1 | 3 | 2 | 1 | 3 | 0 | 1 | 0 |
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"]
}