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

Sublime​Linter-csslint

by SublimeLinter ST3 Top 100

SublimeLinter plugin for CSS, using csslint.

Details

Installs

  • Total 129K
  • Win 64K
  • OS X 44K
  • Linux 21K
Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 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
Windows 86 114 105 121 93 78 72 97 107 116 136 105 65 83 85 96 106 112 92 61 59 80 87 81 87 76 50 61 76 82 82 79 86 53 64 81 73 101 80 95 65 55 105 98 93 97
OS X 41 30 55 43 39 33 31 48 57 41 48 43 31 34 38 46 55 52 44 31 32 42 38 42 45 37 26 27 41 53 41 56 58 45 31 41 53 52 55 47 33 23 53 62 53 52
Linux 24 21 32 20 27 15 17 18 19 19 23 23 21 9 32 17 25 20 25 13 21 18 13 28 19 20 16 13 20 37 17 27 21 13 12 24 18 25 13 15 14 12 21 22 12 26

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-csslint

This linter plugin for SublimeLinter provides an interface to csslint. It will be used with files that have the “CSS” syntax, or within <style> tags in HTML files.

Installation

SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.

Linter installation

Before installing this plugin, you must ensure that csslint is installed on your system. To install csslint, do the following:

  1. Install Node.js (and npm on Linux).

  2. Install csslint by typing the following in a terminal:

npm install -g csslint
  1. If you are using nvm and zsh, ensure that the line to load nvm is in .zshenv and not .zshrc.

Note: This plugin requires csslint 0.10.0 or later.

Linter configuration

In order for csslint to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter. Before going any further, please read and follow the steps in “Finding a linter executable” through “Validating your PATH” in the documentation.

Once csslint is installed and configured, you can proceed to install the SublimeLinter-csslint plugin if it is not yet installed.

Plugin installation

Please use Package Control to install the linter plugin. This will ensure that the plugin will be updated when new versions are available. If you want to install from source so you can modify the source code, you probably know what you are doing so we won’t cover that here.

To install via Package Control, do the following:

  1. Within Sublime Text, bring up the Command Palette and type install. Among the commands you should see Package Control: Install Package. If that command is not highlighted, use the keyboard or mouse to select it. There will be a pause of a few seconds while Package Control fetches the list of available plugins.

  2. When the plugin list appears, type csslint. Among the entries you should see SublimeLinter-csslint. If that entry is not highlighted, use the keyboard or mouse to select it.

Settings

For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.

In addition to the standard SublimeLinter settings, SublimeLinter-csslint provides its own settings which correspond to the command line options of the same name. All of them may be used as inline overrides.

Setting Description
errors A comma-separated list of rules to include as errors
warnings A comma-separated list of rules to include as warnings
ignore A comma-separated list of rules to ignore

To get a list of the available rule names, execute csslint --list-rules from a terminal.

You may also use any of the csslint configuration options, including .csslintrc files and embedded rules. Please see the csslint documentation for more information.

Contributing

If you would like to contribute enhancements or fixes, please do the following:

  1. Fork the plugin repository.
  2. Hack on a separate topic branch created from the latest master.
  3. Commit and push the topic branch.
  4. Make a pull request.
  5. Be patient. ;-)

Please note that modications should follow these coding guidelines:

  • Indent is 4 spaces.
  • Code should pass csslint and pep257 linters.
  • Vertical whitespace helps readability, don’t be afraid to use it.

Thank you for helping out!