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 137K
  • Win 69K
  • OS X 46K
  • Linux 22K
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 Mar 11
Windows 81 121 66 70 78 103 81 99 89 63 64 99 98 101 74 91 72 71 101 102 91 82 98 62 55 80 92 92 90 88 63 63 107 97 94 133 113 55 69 103 117 80 102 102 62 79
OS X 29 46 30 30 34 40 38 58 52 26 29 39 53 46 39 42 23 27 32 43 44 52 48 31 31 40 40 55 53 39 17 31 45 42 57 35 48 29 29 31 44 59 56 48 35 34
Linux 21 19 14 17 28 24 22 20 17 10 25 24 26 27 23 17 15 24 23 21 19 26 27 14 14 31 30 22 25 33 11 24 16 39 32 17 23 20 18 27 22 23 19 25 19 21

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-csslint

Build Status

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!