The Bjolang grammar is a resource, so bjo publish copies it

The module reads grammars/bjolang from beside its src/, found from its own
DLL. Declared with (resources "grammars"), bjo publish copies it to the same
place relative to the module, and a published program highlights Bjolang.

Version 0.1.1.

🤖 Generated with [ECA](https://eca.dev) (anthropic/claude-opus-5-5)

Co-Authored-By: eca-agent <git@eca.dev>
This commit is contained in:
Linus Björnstam 2026-10-02 14:39:31 +02:00
parent 6bb44bc05f
commit e51b7170a9
2 changed files with 9 additions and 3 deletions

View file

@ -36,8 +36,10 @@
;; - TextMateSharp takes a theme's own rules before the ones it includes,
;; however specific: Light+ colours `this` as a variable, where VS Code
;; gives it the included theme's blue. Both styles here follow TextMateSharp.
;; - The Bjolang grammar is found beside the DLL. A program copied somewhere
;; without grammars/ — what a bjo publish would do — has no bjolang.
;; - The Bjolang grammar is found beside the DLL. The manifest declares
;; grammars/ as a resource, so bjo publish copies it to the same place
;; relative to the module; a program copied by hand without it has no
;; bjolang.
;; - A highlighter tokenizes one line at a time, under a lock: TextMateSharp
;; compiles a grammar's rules as it meets them and says nothing about
;; threads. Parallel work wants a highlighter per thread.