Editor support

Syntax highlighting for lippy (.lip) files. The grammar files live on this site, so they're always the latest — the same ones that ship in the repo.

Kate / KDE

Kate uses a KSyntaxHighlighting XML file. Two files: the grammar and a MIME type so Kate recognises .lip by extension and by #!/usr/bin/env lippy shebang.

mkdir -p ~/.local/share/org.kde.syntax-highlighting/syntax
curl -sSL https://lippy-lang.s3.fr-par.scw.cloud/editors/kate/lippy.xml \
  -o ~/.local/share/org.kde.syntax-highlighting/syntax/lippy.xml

mkdir -p ~/.local/share/mime/packages
curl -sSL https://lippy-lang.s3.fr-par.scw.cloud/editors/kate/lippy-mime.xml \
  -o ~/.local/share/mime/packages/lippy.xml
update-mime-database ~/.local/share/mime

Restart Kate. If you have the repo checked out, make install-kate does the same thing.

VS Code

A TextMate grammar. Drop it into a tiny extension folder:

mkdir -p ~/.vscode/extensions/lippy/syntaxes
curl -sSL https://lippy-lang.s3.fr-par.scw.cloud/editors/vscode/package.json \
  -o ~/.vscode/extensions/lippy/package.json
curl -sSL https://lippy-lang.s3.fr-par.scw.cloud/editors/vscode/syntaxes/lippy.tmLanguage.json \
  -o ~/.vscode/extensions/lippy/syntaxes/lippy.tmLanguage.json

Reload VS Code (Developer: Reload Window). Open a .lip file and it lights up.

Anything else

Both grammars are hand-written and small — worth a read if you're wiring up another editor. Grab them from /editors/ on this site, or from the editors/ folder in the source tree.