From ef78fbd9cefc17da4f4be82545a055ea4c6b591c Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Wed, 4 Nov 2026 23:33:59 -0300 Subject: mouse: a header drag takes its point from headerPoint, as a press does, where it worked the same offset out again line for line; reportGesture, a call of reportRange, is that call at its one caller; Pardes.reprojectBodyHit, which ignored its receiver, is Layer.bodyAgain where it was called; wordAtCol is wordBoundsAtCol sliced at its one caller; seamIdxAt is mouse.zig's own (events.zig's comment names reportRange) Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge --- src/ninep/events.zig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/ninep') diff --git a/src/ninep/events.zig b/src/ninep/events.zig index 1a0e9a86..088520e3 100644 --- a/src/ninep/events.zig +++ b/src/ninep/events.zig @@ -758,7 +758,7 @@ pub fn writeEvent(p: *Pardes, asked: Req, id: usize) Reply { // it takes it. One that came from a write to exec (`F`) was // never a click, and runs as the command it was. // The chorded exec a reader was told of runs with its argument - // (mouse.reportGesture), when it is that range written back. + // (mouse.reportRange), when it is that range written back. .body_exec, .tag_exec => { const pf = &pane.fs; // The two records that follow a chorded exec (its argument -- cgit v1.3