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

Sublime​Linter-chktex

by SublimeLinter ST3

LaTeX linter plugin for SublimeLinter 3, using chktex.

Details

Installs

  • Total 9K
  • Win 4K
  • OS X 2K
  • Linux 2K
Oct 18 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
Windows 2 3 2 1 2 1 0 0 5 3 3 1 5 2 1 1 1 4 2 1 2 1 1 3 4 2 4 4 4 2 4 2 3 1 7 5 5 0 5 1 1 2 4 6 1 1
OS X 4 1 1 1 1 1 3 1 5 1 3 1 5 0 1 0 1 1 2 1 5 0 1 2 1 1 0 2 1 1 4 2 0 2 3 1 3 2 0 2 3 2 1 2 0 1
Linux 2 0 2 0 1 0 3 0 3 0 2 2 1 1 0 1 3 1 1 3 2 1 4 1 2 0 3 2 1 3 0 0 3 2 1 1 1 3 0 3 1 3 2 3 0 1

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-chktex

Build Status

This linter plugin for SublimeLinter provides an interface to ChkTeX. It will be used with files that have use LaTeX (or LaTeXing) 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 installing this plugin, you must ensure that chktex is installed on your system. ChkTeX is available on CTAN and comes with e.g. TeX Live starting with TeX Live 2011, and available for many platforms.

If you are using a TeX distribution which does not include ChkTeX (for example MiKTeX) follow the instructions below to compile ChkTeX manually:

  1. Make sure you don't have any spaces in the path to MikTeX

  2. Install cygwin with the make and gcc compiler packages

  3. Download chktex and save in home directory of cygwin (default is C:\cygwin\home\USER)

  4. In the cygwin bash, run

    cd c:
    cd cygwin64/home/USER
    cd chktex-1.7.2
    configure
    make
    make install
    
  5. The resulting chktex.exe along with cygwin1.dll should now be saved in a directory which is registered in the PATH environment variable (for example %MiKTeX Install%\miktex\bin\ is appropriate)

Linter configuration

In order for chktex 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 chktex is installed and configured, you can proceed to install the SublimeLinter-chktex 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 chktex. Among the entries you should see SublimeLinter-chktex. 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-chktex provides its own settings, which may also be used inline as overrides. For a full list of warnings see the ChkTeX manual.

By default, SublimeLinter-chktex ignores Warning 22 (Comment displayed) and Warning 30 (Multiple spaces detected in output). It also sets Warning 16 (Mathmode is still on at end of LaTeX file) as an error.

Setting Description Default
nowarn A comma-separated list of warnings to ignore. [22,30]
erroron A comma-separated list of warnings to output as errors. [16]

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.

Thank you for helping out!