Main SYNX site: https://synx.aperturesyndicate.com/
Syntax highlighting + LSP (synx-lsp) for the SYNX format.
Manual (recommended for development)
- Preferences → Browse Packages…
- Create folder
Synx(or clone this repo pathintegrations/sublime-text/SynxintoPackages/Synx). - Restart Sublime Text.
You should see synx.sublime-syntax and this README.md in the package folder.
Optional — via Git on your machine
# Example: clone repo and symlink into Sublime’s Packages (path varies by OS)
ln -s /path/to/synx-format/integrations/sublime-text/Synx ~/Library/Application\ Support/Sublime\ Text/Packages/SynxPublishing to Package Control later: submit a PR to Package Control channel with your public Git URL, or document your own repository URL in repositories.json (see Package Control docs).
Open any *.synx file — if association is wrong, use View → Syntax → SYNX (after the package is installed).
The bundled synx.sublime-syntax covers directives (!active, !include, …), comments, keys, markers, lists.
- Install LSP via Package Control.
- Build or install
synx-lspso it is onPATH(seecrates/synx-lsp/README.md). - Open Preferences → Package Settings → LSP → Settings, merge:
{
"clients": {
"synx-lsp": {
"enabled": true,
"command": ["synx-lsp"],
"selector": "source.synx",
"file_patterns": ["*.synx"]
}
}
}On Windows, if synx-lsp is not on PATH, use the full path:
"command": ["C:\\path\\to\\synx-lsp.exe"]- Open a
.synxfile — LSP should start automatically (check LSP log panel if not).
- Package Control: follow official instructions (tags
st3-4.0, readablepackage.json-style meta, or legacy channel submission). - Manual: ship a
.zipof this folder and ask users to unzip intoPackages/Synx.
Keep the package small: do not commit Sublime’s Cache or workspace files.