Orkuncakilkaya e3e1bc7784 fix(tools): formatter bracket rules, LSP compiler diagnostics, vocabulary sync

- ludic-fmt: `rows[i]`, `new []int`, `s[a..b]`, `emit(`, `~x`, list-literal
  and query-tag braces stay tight; member calls hug their paren
  (`Date.new(`, `Prefab.spawn(`); `<< >> & | ^ ~` are operators and
  `&& ||` are not — mirrored in ludic_syntax.h, LudicLexer.kt and the
  TextMate grammar. 149 of 274 tracked sources failed --check before.
- ludic-lsp: `initializationOptions.compilerDiagnostics` / `compilerPath`
  are honoured — on save the document's compilation unit is compiled and
  `file:line: error: msg` is published as a "ludicc" diagnostic (the
  option had been documented but never implemented); the workspace scan
  file is per process; bracket codes spelled as char literals
- Overlay added to LUDIC_PHASES, LudicTokens.kt, ludic-mode.el and the
  grammar (the game uses it; check-vocabulary flagged the drift)
- editors: VS Code snippets/package.json/extension.js (`${workspaceFolder}`
  and `~` expansion, PATH lookup, Apache-2.0, real repo URL), Neovim root
  markers, Helix/Zed/Sublime bin/ paths, Emacs vocabulary, JetBrains
  comments; tools/editors/README.md no longer describes C tooling
- .forgejo workflows clone `${{ github.server_url }}/${{ github.repository }}`
  so a fork or mirror tests itself; the docs publish pushes the same way

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-05 01:12:26 +03:00

2 KiB

Raw Blame History

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:

bin/x tools

That produces bin/ludic-lsp and bin/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 (~ and ${workspaceFolder} expand). Empty = search bin/, then PATH.
ludic.server.enabled — turn the server off and keep only static highlighting.
ludic.compilerPath — where ludicc lives, for on-save diagnostics (~ and ${workspaceFolder} expand).
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

2 KiB Raw Blame History