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

Sublime​Linter-contrib-pug-lint

by benedfit ST3

SublimeLinter plugin for Pug (formerly Jade), using pug-lint

Details

Installs

  • Total 8K
  • Win 4K
  • OS X 2K
  • Linux 1K
Oct 17 Oct 16 Oct 15 Oct 14 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
Windows 14 14 4 4 14 11 3 8 7 1 5 3 9 4 8 5 3 8 6 6 12 6 12 7 7 6 5 6 13 17 4 4 8 9 7 6 6 6 5 6 11 7 9 5 6 10
OS X 4 4 3 2 4 0 2 7 3 2 0 4 3 1 5 5 5 5 2 2 9 5 3 3 4 4 3 7 8 10 3 4 5 2 2 2 3 1 2 1 3 5 9 3 2 1
Linux 1 1 5 1 0 2 0 2 3 1 2 2 0 1 2 0 0 2 3 1 2 2 1 0 0 3 3 5 0 0 1 2 0 2 2 2 1 0 1 3 4 1 3 2 1 1

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-contrib-pug-lint

Build Status

This linter plugin for SublimeLinter provides an interface to pug-lint. It will be used with files that have the “pug” syntax.

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 using this plugin, you must ensure that pug-lint is installed on your system. To install pug-lint, do the following:

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

  2. Install pug-lint by typing the following in a terminal:

npm install -g pug-lint

Note: This plugin requires pug-lint 2.1.1 or later.

Linter configuration

In order for pug-lint 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 you have installed and configured pug-lint, you can proceed to install the SublimeLinter-contrib-pug-lint 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 pug-lint. Among the entries you should see SublimeLinter-contrib-pug-lint. 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.

You can configure pug-lint options in the way you would from the command line, with .pug-lintrc files. For more information, see the pug-lint docs. The linter plugin does this by searching for a .pug-lintrc file in your stylus file’s current directory tree. If you are an OSX / Linux user, you can also set a global .pug-lintrc in your User (~) directory.

You may provide a custom config file by setting the linter’s "args" setting to ["--config", "/path/to/file"]. On Windows, be sure to double the backslashes in the path, for example ["--config", "C:\\Users\\Name\\pug-lint.conf"].

The path to the .pug-lintrc file is cached, meaning if you create a new .pug-lintrc that should have precedence over the previous one (meaning it is closer to the .pug file) you need to clear the cache for the linter to use the new .pug-lintrc You can clear the cache by going to: Tools > SublimeLinter > Clear Caches.

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 modifications should follow these coding guidelines:

  • Indent is 4 spaces.
  • Code should pass flake8 and pep257 linters.
  • Vertical whitespace helps readability, don’t be afraid to use it.
  • Please use descriptive variable names, no abbreviations unless they are very well known.

Thank you for helping out!