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

Sublime​Linter-contrib-makensis

by idleberg ST3

This linter plugin for SublimeLinter provides an interface to makensis

Details

Installs

  • Total 350
  • Win 171
  • OS X 99
  • Linux 80
Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14 May 13 May 12 May 11 May 10 May 9
Windows 0 0 0 0 0 0 0 1 1 1 0 3 0 0 1 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
OS X 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 1 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-contrib-makensis

The MIT License Package Control GitHub Travis CI

This linter plugin for SublimeLinter provides an interface to makensis. It will be used with NSIS scripts.

Screenshot

Linter in action (using Hopscotch color scheme)

Installation

SublimeLinter 4 must be installed in order to use this plugin. If SublimeLinter 4 is not installed, please follow the instructions here.

Linter installation

Before using this plugin, you must ensure that NSIS v3.02.1 (or higher) is installed on your system. To install it, do the following:

Windows

Download the NSIS installer from SourceForge and run setup. Make sure makensis is in your PATH environmental variable.

Alternatively, you can install NSIS through Chocolatey:

choco install nsis

Linux

Install NSIS from your distribution's default package manager, for example:

# Debian
sudo apt-get -t experimental install nsis

# Red Hat
sudo dnf install nsis

macOS

Install NSIS using Homebrew or MacPorts:

# Homebrew
brew install nsis

# MacPorts
port install nsis

Note: As of v3.02.1, the macOS builds should use the correct version string rather than build date

Linter Configuration

In order for makensis 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 makensis, you can proceed to install the SublimeLinter-contrib-makensis 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 makensis. Among the entries you should see SublimeLinter-contrib-makensis. If that entry is not highlighted, use the keyboard or mouse to select it.

Plugin Configuration

To configure this plugin, bring up the Command Palette and type Preferences: SublimeLinter Settings. The following options are available:

Option Default Description
ppo true Lints much faster, but ignores warning (equivalent of -PPO flag)
strict false Treats warnings as errors (equivalent of -WX flag)

Example:

{
  "linters": {
    "makensis": {
      "@disable": false,
      "args": [],
      "excludes": [],
      "ppo": true,
      "strict": false
    }
  }
}

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!