SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.
Before installing this plugin, you must ensure that
jsl 0.3.0 is installed on your system. To install
NOTE: Do not use the latest development version from svn. This plugin is only compatible with one of the 0.3.0 releases.
In order for
jsl 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.
jsl is installed and configured, you can proceed to install the SublimeLinter-jsl plugin if it is not yet installed.
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:
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.
When the plugin list appears, type
jsl. Among the entries you should see
SublimeLinter-jsl. If that entry is not highlighted, use the keyboard or mouse to select it.
You can configure
jsl options in the way you would from the command line, with
jsl.conf files. For more information, see the jsl docs. The linter plugin does this by searching for a
jsl.conf file itself in the linted file's working directory, its parent directories, and the user's home directory (
You may provide a custom config file by setting the linter's
"args" setting to
["-conf", "/path/to/file"]. To create a
jsl config file, type the following in a terminal:
jsl -help:conf > jsl.conf
If you would like to contribute enhancements or fixes, please do the following:
- Fork the plugin repository.
- Hack on a separate topic branch created from the latest
- Commit and push the topic branch.
- Make a pull request.
- Be patient. ;-)
Please note that modications 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!