BridleNSIS syntax definitions and completions for Sublime Text
- Total 245
- Win 203
- OS X 22
- Linux 20
|Dec 13||Dec 12||Dec 11||Dec 10||Dec 9||Dec 8||Dec 7||Dec 6||Dec 5||Dec 4||Dec 3||Dec 2||Dec 1||Nov 30||Nov 29||Nov 28||Nov 27||Nov 26||Nov 25||Nov 24||Nov 23||Nov 22||Nov 21||Nov 20||Nov 19||Nov 18||Nov 17||Nov 16||Nov 15||Nov 14||Nov 13||Nov 12||Nov 11||Nov 10||Nov 9||Nov 8||Nov 7||Nov 6||Nov 5||Nov 4||Nov 3||Nov 2||Nov 1||Oct 31||Oct 30|
BridleNSIS for SublimeText
BridleNSIS is a language extension for NSIS designed to make things easier to express and rein in verbosity of NSIS at places.
- Make sure you already have Package Control installed
- Choose “Install Package” from the Command Palette (Super+Shift+p)
- Type “BridleNSIS” and press Enter
With auto_upgrade enabled, Package Control will keep all installed packages up-to-date!
- Change to your Sublime Text
- Clone repository
git clone https://github.com/idleberg/sublime-bridlensis.git BridleNSIS
- Download the latest stable release
- Unzip the archive to your Sublime Text
To avoid interference with vanilla NSIS, consider using the file-extensions
.bridle-nsh. Alternatively, you can set the syntax to “BridleNSIS” (
Since all BridleNSIS commands match their vanilla NSIS equivalents, the completions are prefixed with
b:. While Sublime Text's fuzzy search doesn't require you to type the prefix, you might get quicker results doing so, especially for commands such as
If, which could be confused with the compile-time command
!if or the LogicLib macro
On Windows, you can build your script using the default Superb. If you have any build systems for vanilla NSIS installed, you might have to switch to BridleNSIS before building.
This work is licensed under the The MIT License.
You are welcome support this project using Flattr or Bitcoin