ok2
a66435c93c
The syntax file landed inbcccdfb, one commit before `(LOCAL)` and while several other recently-added words were already in the tree but unhighlighted. Extend it to cover everything currently registered. Added contexts: - `locals` — `{:` `:}` `{F:` `TO` `LOCALS|` `END-LOCALS` `(LOCAL)`. - `structures` — `BEGIN-STRUCTURE` (captures the following name), `END-STRUCTURE`, `+FIELD`, `FIELD:`, `CFIELD:`, `FFIELD:`, `SFFIELD:`, `DFFIELD:`. - `hashing` — `SHA1`, `SHA256`, `SHA512`. Comment notes the list mirrors `crypto::ALGOS`. Extended: - `definitions` — quotations `[:` / `;]` (Core-ext 6.2.0455). - `parsing` — state-smart `S` (the string parser fromd1a7d55). - `wafer_extras` — `READ-PASSWORD` (web-side prompter from9150696). Context order in `main:` keeps `definitions` ahead of `locals`, so `: foo` still wins over `{:` / `:}`, and `strings` / `arithmetic` stay ahead of `parsing` so `S"` and `S>D` keep their existing highlighting despite the new bare-`S` rule.
Editor support for WAFER
Syntax highlighting assets for editors and pagers.
bat (and other Sublime-Text-compatible tools)
bat/WAFER.sublime-syntax is a Sublime Text grammar covering Forth 2012 plus
WAFER-specific words (CONSOLIDATE, RANDOM, RND-SEED, UTIME).
Install
just install-syntax
or manually:
mkdir -p ~/.config/bat/syntaxes
cp tools/editor-support/bat/WAFER.sublime-syntax ~/.config/bat/syntaxes/
bat cache --build
Verify
bat --list-languages | grep -i forth # should list Forth
bat --language forth crates/core/boot.fth # should render with colour
Use with oked
oked auto-detects .fth / .4th / .forth files and invokes bat with
--language forth. After the install step above, opening any WAFER source in
oked and toggling highlight (H command, or oked -S forth) will use this
syntax.
Updating the keyword list
Primitives live in crates/core/src/outer.rs (register_primitive and
register_host_primitive calls). When a new user-facing, non-standard word
is added, append it to the wafer_extras context in
bat/WAFER.sublime-syntax. Standard Forth 2012 words are already covered by
the main contexts.
Internal symbols (names that start with _) should not be added — they are
implementation details that user code never types.