From 4c4fce7373ea72b10e8d9bb7aa3c91c3d5bbf0f5 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Sun, 8 Nov 2026 22:05:53 -0300 Subject: helix: the page-scroll mismatches were the view's height, not a rule: pardes's scroll (Text.scrollViewMove, halfPageMove, gotoWindow) is helix's commands.rs scroll/page_* rule for rule, but hxdiff ran pardes at 80x24, where its chrome leaves the pane 21 rows to helix's 22 (half page 10 to 11, page 21 to 22); the harness runs the core at 80x25 so the pane is helix's 22 and refuses a case whose pane is not, and helix-keys.md says why: hxdiff's twelve page-scroll cases and gb-after-zz pass (16 to 3), hxparity's five page waivers match again (5 to 0) Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge --- docs/helix-keys.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs/helix-keys.md') diff --git a/docs/helix-keys.md b/docs/helix-keys.md index 4e543bbb..f517a7a8 100644 --- a/docs/helix-keys.md +++ b/docs/helix-keys.md @@ -442,7 +442,10 @@ Files (all in `test/hxcases/`): no script. Either wire it up or delete it. The pardes half is `test/hxdiff.zig`, which builds `pardes-hxdiff` and drives -the core headlessly at 80x24 (22 body rows, matching helix's 22 text rows). +the core headlessly at 80x25: helix's harness runs at 80x24, whose one view +is 22 text rows, and pardes's chrome takes a row more, so its pane gets the +same 22. Every page key, half page, `zz` and `gb` counts in those rows, so +the harness refuses to run a case whose pane shows any other number. Run it: -- cgit v1.3