SublimeLinter-contrib-codespell
Adapter for SublimeLinter to codespell
Details
Installs
- Total 433
- Win 267
- Mac 107
- Linux 59
| Oct 13 | Oct 12 | Oct 11 | Oct 10 | Oct 9 | Oct 8 | Oct 7 | Oct 6 | Oct 5 | Oct 4 | Oct 3 | Oct 2 | Oct 1 | 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 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 2 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Mac | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Linux | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
SublimeLinter-contrib-codespell
This linter plugin for SublimeLinter provides an interface to codespell.
Installation
SublimeLinter must be installed in order to use this plugin. Install via Package Control or git clone as usual.
Ensure that a codespell is actually installed somewhere on your system. Typically,
pip install codespell
on the command line will do that.
Notes
This plugin registers codespell for all views. You can restrict that, e.g. you can set
"codespell": {
"selector": "-text.plain",
},
in SublimeLinter's main settings (Preferences: SublimeLinter Settings) to
ignore plain text files. This can also be set per project or even per view
under the setting name SublimeLinter.linters.codespell.selector.
Esp. for this linter I'm used to show the correct/fixed spelling on the ride side of the view. You can enable that via
"codespell": {
"styles": [
{
"scope": "region.redish", # any color you like
"annotation": "{msg}", # configure right hand side annotation
"phantom": "" # disable phantoms
}
]
},
There is also a quick-fix available if (and only if) codespell suggests exactly one other spelling. That means, if you have setup a key-binding, e.g. the one suggested in the SublimeLinter's README
// To trigger a quick action
// { "keys": ["ctrl+k", "ctrl+f"],
// "command": "sublime_linter_quick_actions"
// },
you can basically fix a misspelled word on the line of the cursor by typing
ctrl+k, ctrl+f. (You don't need to be on the word, btw! Handy.)