https://github.com/idleberg/sublime-nsl-assembler
nsL Assembler syntax definitions and build system for Sublime Text
https://github.com/idleberg/sublime-nsl-assembler
bridlensis nsis nsl nsl-assembler sublime-build sublime-completions sublime-syntax sublime-text tmlanguage transpiler
Last synced: 25 days ago
JSON representation
nsL Assembler syntax definitions and build system for Sublime Text
- Host: GitHub
- URL: https://github.com/idleberg/sublime-nsl-assembler
- Owner: idleberg
- License: mit
- Created: 2014-04-08T17:53:41.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2020-08-11T13:39:12.000Z (almost 5 years ago)
- Last Synced: 2025-04-27T10:06:04.847Z (25 days ago)
- Topics: bridlensis, nsis, nsl, nsl-assembler, sublime-build, sublime-completions, sublime-syntax, sublime-text, tmlanguage, transpiler
- Language: Batchfile
- Homepage:
- Size: 604 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# nsL Assembler for SublimeText
[](http://opensource.org/licenses/MIT)
[](https://packagecontrol.io/packages/nsL%20Assembler)
[](https://github.com/idleberg/sublime-nsl-assembler/releases)
[](https://travis-ci.org/idleberg/sublime-nsl-assembler)
[](https://gitter.im/NSIS-Dev/SublimeText)
[nsL Assembler](http://sourceforge.net/projects/nslassembler/) syntax definitions, command completions and build system for [Sublime Text](http://www.sublimetext.com/).
nsL is a new C-like programming language for writing [NSIS](http://nsis.sourceforge.net) 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](http://www.sublimetext.com/blog/articles/sublime-text-3-build-3103) or higher). Click [here](https://github.com/idleberg/sublime-nsl-assembler/tree/subl2) for a Sublime Text 2 version of this package.
*Screenshot using [Hopscotch](https://github.com/idleberg/Hopscotch) color scheme*
## Installation
### Package Control
1. Make sure you already have [Package Control](https://packagecontrol.io/) installed
2. Choose *“Install Package”* from the Command Palette (Super+Shift+p)
3. Type *“nsL Assembler”* and press Enter
With [auto_upgrade](http://wbond.net/sublime_packages/package_control/settings/) enabled, Package Control will keep all installed packages up-to-date!
### Using Git
1. Change to your Sublime Text `Packages` directory
2. Clone repository `git clone https://github.com/idleberg/sublime-nsl-assembler.git 'nsL Assembler'`
### Manual installation
1. Download the latest [stable release](https://github.com/idleberg/sublime-nsl-assembler/releases)
2. Unzip the archive to your Sublime Text `Packages` directory
## Usage
### Completions
You can complete all nsL (and NSIS) commands using the `Tab` key. Hit `Tab` again to jump between fields.
### Scaffolding
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 Script`snippet and create the following script:
```cpp
// 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.
### Building
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](http://superuser.com/a/284351/195953) `%NSIS_HOME%`. In case of a *Permission denied* error, change the permissions of the Bash script: `chmod +x build.sh`.
## License
This work is licensed under the [The MIT License](LICENSE).