Skip to content

Hot-reload all current ZeroSyntax settings #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ViTeXFTW merged 3 commits into from
Jul 18, 2026
Merged

Hot-reload all current ZeroSyntax settings #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4dff954
Hot-reload ZeroSyntax settings
ViTeXFTW Jul 18, 2026
ef253c9
Satisfy Clippy
ViTeXFTW Jul 18, 2026
76a7e99
Normalize VS Code settings sync
ViTeXFTW Jul 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,11 +138,14 @@ schema.json ──embedded──▶ schema ──▶ analysis ──▶ server
`WorkspaceIndex`. `convert.rs` does byte-offset ↔ LSP position mapping in
the position encoding negotiated at `initialize` (UTF-8 when the client
offers it, else the UTF-16 baseline). Advertises `semanticTokens` `full`
**and** `range`. Formatting is **opt-in**: the capability is advertised
only when `initializationOptions` carries `{"format": {"enable": true}}`
(the VS Code setting `zerosyntax.format.enable`, default off — real game
files are wildly hand-indented, so format-on-save must never fire
unasked). Phase-3 numbers (`docs/phase3-incremental.md`): keystroke on the
**and** `range`. Runtime settings arrive through initialization options and
`workspace/didChangeConfiguration`; analysis switches refresh open docs,
while schema/base-root changes replace the complete index and reparse only
when the schema changes. Formatting is **opt-in** and dynamically registered
when supported (the VS Code setting `zerosyntax.format.enable`, default off —
real game files are wildly hand-indented, so format-on-save must never fire
unasked). Only the executable-path setting requires a client restart.
Phase-3 numbers (`docs/phase3-incremental.md`): keystroke on the
61k-line ParticleSystem.ini ≈ 147 µs vs 44 ms full reparse.

### Two concepts worth understanding before editing
Expand Down
Loading