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 146K
  • Win 74K
  • OS X 48K
  • Linux 24K
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 Jul 14 Jul 13 Jul 12 Jul 11 Jul 10 Jul 9 Jul 8 Jul 7 Jul 6 Jul 5 Jul 4 Jul 3 Jul 2 Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12
Windows 20 80 92 89 49 53 82 80 80 92 78 40 47 67 76 78 80 81 57 49 69 98 74 77 73 55 59 79 85 69 73 80 41 57 70 73 91 88 66 43 42 66 87 71 80 73
OS X 6 43 34 32 19 27 33 40 34 27 39 14 28 39 33 44 45 37 22 31 50 39 47 31 33 35 25 31 37 38 45 38 21 21 42 23 33 35 35 20 39 42 40 41 44 31
Linux 7 13 17 19 13 14 15 11 18 18 9 14 12 18 20 12 22 13 13 13 27 16 11 29 25 11 11 16 18 22 18 20 7 9 15 33 20 20 14 15 12 24 27 11 23 19

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!