ludic/tools/editors/vscode
Orkuncakilkaya 42f955fd22 Phase 6a: rename core vocabulary (game/main/component/archetype/system)
game/module -> program, main -> entry, component -> property,
archetype -> model, system -> handler. Done via a transitional self-hosting
bootstrap: parser accepts both -> reseed -> compiler source moved to new
keywords + parser tightened to new-only -> reseed (fixpoint holds). Old keywords
now rejected.

Token-safe corpus migration (tools/ludic-tools/rename_kw.c) leaves the LLVM
@main/entry: labels in emit strings untouched; goldens byte-identical. Editor
vocab (header/JetBrains/TextMate/emacs), check-docs wrapper, and doc fences
updated; error string 'unknown component' -> 'unknown property'. test.sh 14/14,
test-tools 28/0, check-vocabulary green. (Doc prose pass to follow.)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-08-27 18:22:13 +03:00
..
icons Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete 2026-08-27 15:15:35 +03:00
snippets Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete 2026-08-27 15:15:35 +03:00
src Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete 2026-08-27 15:15:35 +03:00
syntaxes Phase 6a: rename core vocabulary (game/main/component/archetype/system) 2026-08-27 18:22:13 +03:00
.vscodeignore Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete 2026-08-27 15:15:35 +03:00
language-configuration.json Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete 2026-08-27 15:15:35 +03:00
package-lock.json Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete 2026-08-27 15:15:35 +03:00
package.json Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete 2026-08-27 15:15:35 +03:00
README.md Baseline: Ludic compiler + toolchain, Phase 1 syntax fixes complete 2026-08-27 15:15:35 +03:00

Ludic for VS Code

Syntax highlighting, formatting, and full language-server support for Ludic, the AI-first, ECS-native game language. See LANGUAGE.md in the Ludic repository for the language reference.

What you get

Source
Syntax highlighting TextMate grammar, works with no build
Semantic highlighting ludic-lsp — real name resolution, so a component reads differently from a local
Diagnostics structural errors as you type; ludicc's own errors on save
Completion context-aware: fields after ., components inside query [...], phases after phase, widgets inside ui
Hover signatures and docs for builtins, intrinsics, and everything you declared
Go to definition / references / rename across every file in the compilation unit, following import
Formatting format-on-save, comment-preserving
Outline, folding, inlay hints, signature help
```ludic fences in Markdown highlighted, checked, and formatted

Setup

Build the toolchain once, from the repository root:

./tools/build-tools.sh

That produces build/ludic-lsp and build/ludic-fmt, which the extension finds on its own. If you keep them elsewhere, set ludic.server.path.

Format on save:

"[ludic]": { "editor.formatOnSave": true }

Settings

  • ludic.server.path — where ludic-lsp lives. Empty = search build/, then PATH.
  • ludic.server.enabled — turn the server off and keep only static highlighting.
  • ludic.compilerPath — where ludicc lives, for on-save diagnostics.
  • ludic.compilerDiagnostics — whether to run the compiler at all.
  • ludic.indentSize — spaces per level for the formatter.
  • ludic.trace.server — log LSP traffic (Ludic: Show Language Server Log).

Installing without publishing

cd tools/editors/vscode
npm install
npx @vscode/vsce package
code --install-extension ludic-1.0.0.vsix