ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Sublime​Linter-contrib-codespell

by kaste ST3

Adapter for SublimeLinter to codespell

Details

  • 1.0.2
    1.0.1
  • github.​com
  • github.​com
  • 12 months ago
  • 34 minutes ago
  • 3 years ago

Installs

  • Total 423
  • Win 261
  • Mac 105
  • Linux 57
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 Aug 15 Aug 14 Aug 13 Aug 12 Aug 11 Aug 10 Aug 9 Aug 8 Aug 7 Aug 6 Aug 5 Aug 4 Aug 3 Aug 2 Aug 1 Jul 31 Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15
Windows 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0
Mac 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 0 0 0 0 0 0 0 0 1 0 0 0
Linux 0 0 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 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

Error: language “jsonc” is not supported
// 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.)