nsL Assembler syntax definitions, command completions and build system for Sublime Text.
nsL is a new C-like programming language for writing NSIS installation wizards. The nsL assembler takes nsL code and translates it into original NSIS script which can then be compiled.
Note: This package is compatible with Sublime Text 3 (Build 3103 or higher). Click here for a Sublime Text 2 version of this package.
Screenshot using Hopscotch color scheme
- Make sure you already have Package Control installed
- Choose “Install Package” from the Command Palette (Super+Shift+p)
- Type “nsL Assembler” and press Enter
With auto_upgrade enabled, Package Control will keep all installed packages up-to-date!
- Change to your Sublime Text
Packagesdirectory - Clone repository
git clone https://github.com/idleberg/sublime-nsl-assembler.git 'nsL Assembler'
- Download the latest stable release
- Unzip the archive to your Sublime Text
Packagesdirectory
You can complete all nsL (and NSIS) commands using the Tab key. Hit Tab again to jump between fields.
Scaffolding snippets start with the prefix scaffold followed by the type of script you'd like to build:
- Basic Script
- MUI2 Script
Example:
With Sublime Text's fuzzy search in mind, you could for instance type scaffBasic to trigger the scaffold:Basic Scriptsnippet and create the following script:
// Scaffolding by https://github.com/idleberg/sublime-nsl-assembler
// Settings ---------------------------------
Name("installer_name");
OutFile("installer_name.exe");
RequestExecutionLevel(user);
InstallDir($PROGRAMFILES . "\\installer_name");
// Includes ---------------------------------
// Pages ------------------------------------
page Components();
page Directory();
page InstFiles();
// Sections ---------------------------------
section section_index("section_name") {
// your code here
}
// Functions --------------------------------Use Tab to jump to the next relevant bit of code you might want to change, Shift-Tab to jump back.
You can build your script using the default shortcut or from the Tools menu. Output scripts will be placed in the same folder as your input. Note that as of Windows Vista you need administrative rights to compile scripts in %PROGRAMFILES%, which is the default location for nsL example scripts!
Should the build system be unable to locate the compiler, you should probably re-install NSIS to make sure required registry keys are created. Alternatively, you can specify the install location in the environment variable %NSIS_HOME%. In case of a Permission denied error, change the permissions of the Bash script: chmod +x build.sh.
This work is licensed under the The MIT License.