summaryrefslogtreecommitdiff
path: root/docs/lsp.md
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-29 22:58:53 -0300
committerGabriel Schneider <[email protected]>2026-10-01 00:12:17 -0300
commitb1485c97b493f7eaf65c6afdfb82e3065306b8fe (patch)
tree890d411820859ef33f1adf3164176fe29e007961 /docs/lsp.md
parentf0e162d287f44a562ff79e7c1d2cf81ace00c836 (diff)
downloadpardes-b1485c97b493f7eaf65c6afdfb82e3065306b8fe.tar.gz
pardes-b1485c97b493f7eaf65c6afdfb82e3065306b8fe.zip
The PDF benches share their clock, fatal exit, hash, count parser and effect drain, and lspprobe is lspbench's probe subcommand
B4: test/bench_util.zig holds what pdf_bench, pdf_pointer_bench, pdf_scroll_bench and pdf_sections_bench each copied (nowNs x4, fatal x3 named per bench, mix x3, parsePositive/parseCount x3, drainEffects x2). They stay four entry points: pdf_bench links its own mupdf module (with its C source and c_heap) where the others link the core's, which one executable cannot import under one name, and their reports and identities are each bench's own. pdf_sections_bench had rotted since the pane's cursor and selections moved to its body and the render revision became next_raster_revision; it builds and runs again. C6: tools/lspprobe.zig is lspbench's `probe` subcommand (zig build lspbench -- probe <kind> <file> <line>:<col>), and the lspprobe build step goes; docs/lsp.md names the new command. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to 'docs/lsp.md')
-rw-r--r--docs/lsp.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/lsp.md b/docs/lsp.md
index ae350156..22cf1b90 100644
--- a/docs/lsp.md
+++ b/docs/lsp.md
@@ -51,7 +51,7 @@ position encoding, and handles both push and pull diagnostics. Startup and
request waits have deadlines; failed starts back off before retrying. Worker
status messages reach the host event queue.
-`zig build lspprobe -- gd <file> <line>:<column>` queries the same backend from
+`zig build lspbench -- probe gd <file> <line>:<column>` queries the same backend from
the command line. `zig build lspbench` measures it. The Zig snapshot tests
(lsp, lspcomplete, lspdebug and the rest) run the real `zls`; the protocol
ones use a Zig mock server with deterministic answers while exercising the real client,