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