A look takes acme's file:addr and :addr, and one that finds nothing changes nothing

A look at `file:/re/` or `:/re/` searched for the words instead of addressing, and a miss left an empty +Search pane and a cleared selection, while a hit answered the +Search pane on /look. Now an address after a colon (acme look.c:450) is evaluated in the file from its dot; a miss says no match and leaves the panes and the selection alone; a hit reads back as the pane the text is selected in. Both live in lookAt's one flow, so they are one change.

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

1 files changed, 2 insertions, 2 deletions

diff --git a/test/pdf.zig b/test/pdf.zig
index 47f8a9e8..2699fe01 100644
--- a/test/pdf.zig
+++ b/test/pdf.zig
@@ -883,7 +883,7 @@ test "MuPDF pane renders, navigates, searches, and round-trips its page" {
     try std.testing.expect(pane.pdf.?.document_scroll_y > before_height_scroll);
 
     const revision_before_search = active_raster.revision;
-    try pardes.look.runSearch(p, 0, "Pardes", .text, .top);
+    _ = try pardes.look.runSearch(p, 0, "Pardes", .text, .top, true);
     try std.testing.expectEqualStrings("Pardes", pane.pdf.?.search_query);
     try std.testing.expectEqual(revision_before_search, active_raster.revision);
     const results_id = pane.search_pane orelse return error.MissingPdfSearchResults;
@@ -1579,7 +1579,7 @@ test "PDF n/N addresses and reveals distinct MuPDF hits on one page" {
 
     p.locations_config.context = 2;
     p.locations_config.tscontext = true;
-    try pardes.look.runSearch(p, 0, "Pardes", .text, .top);
+    _ = try pardes.look.runSearch(p, 0, "Pardes", .text, .top, true);
     const results_id = pane.search_pane orelse return error.MissingPdfSearchResults;
     const results = p.panes[results_id].?.file.?;
     var found: [3]bool = @splat(false);