A looked word selects its next place in its own pane, as acme's look3

A plain word looked at (a look write, a right click, an ML record written
back) opened another identically named +Search pane each time, until the
panes ran out, and never wrapped. As acme's look3 searches the text for
it (look.c:210), it now selects the word's next place in that pane after
the dot, wrapping at the end, and opens nothing. LookWord list, a new
root setting, keeps the +Search listing (search is the default); the
rsearch snapshot and an output test that walk the listing say LookWord
list. (The leader-path check over every builtin gets a comptime
branch quota, as one more builtin took the GUI build past the default.)

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 1 insertions, 0 deletions

diff --git a/test/output.zig b/test/output.zig
index f3e61e93..478f1b4a 100644
--- a/test/output.zig
+++ b/test/output.zig
@@ -862,6 +862,7 @@ test "n/N resumes the result output whose Look moved focus away" {
     const p = try Pardes.init(std.testing.allocator, .{ .file = path, .cols = 80, .rows = 24 });
     defer p.deinit();
     p.locations_config.layout = .@"inline";
+    p.settings.look_word = .list; // the +Search listing is what is walked
 
     try std.testing.expect(p.executeBuiltinLine(0, "Look target"));
     const rid = p.panes[0].?.search_pane orelse return error.MissingResults;