summaryrefslogtreecommitdiff
path: root/test/snapshots/find.snap
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-08-01 22:44:11 -0300
committerGabriel Schneider <[email protected]>2026-08-10 09:17:07 -0300
commitcbcdf01764e2e144a821643c3a8e9a5ad39eda2e (patch)
tree9b4f45a5e2cc988b2cac1b3606379e682885c5a1 /test/snapshots/find.snap
parent0ef86a17988cac1e09cea2d0b5d80a21e81d7a2e (diff)
downloadpardes-cbcdf01764e2e144a821643c3a8e9a5ad39eda2e.tar.gz
pardes-cbcdf01764e2e144a821643c3a8e9a5ad39eda2e.zip
search look goldens: fsearch/grep/psearch/rsearch updated
Diffstat (limited to 'test/snapshots/find.snap')
-rw-r--r--test/snapshots/find.snap7
1 files changed, 5 insertions, 2 deletions
diff --git a/test/snapshots/find.snap b/test/snapshots/find.snap
index 5a4d6a38..c1467d89 100644
--- a/test/snapshots/find.snap
+++ b/test/snapshots/find.snap
@@ -78,8 +78,11 @@ stable 700 10000
key n
stable 400 5000
snap nomatch
-# ... and it grows BACK when the next search finds more: the refit trades rows
-# with the neighbour in both directions, so three hits are three rows again
+# ... and asking for `zqm` AGAIN re-arms the list it ALREADY filled instead of
+# stacking an identical twin under the empty one — even though n/N were armed
+# on the zzqq list, so the reuse is by what a buffer HOLDS (this search, this
+# pattern, this directory), not by which one the pane happens to point at. The
+# frame is therefore the `results` frame unchanged, down to the byte.
key space
key f
key f