summaryrefslogtreecommitdiff
path: root/test/snapshots/rsearch.snap
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-28 19:52:50 -0300
committerGabriel Schneider <[email protected]>2026-10-01 00:12:15 -0300
commit6a49974e56521cf66c9a4d0eb579cd5de949891e (patch)
treeea2e13f5f35e0ce4bbec209ce59d3f5fe5a4852e /test/snapshots/rsearch.snap
parent197fe7396e7f63e9471bb317f1341228a0690ce6 (diff)
downloadpardes-6a49974e56521cf66c9a4d0eb579cd5de949891e.tar.gz
pardes-6a49974e56521cf66c9a4d0eb579cd5de949891e.zip
Snapshots and GUI goldens run with the default Placement acme
Their clicks follow the panes to where acme's placement puts them; doccol and splitparent stay on Placement pardes, which they cover. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to 'test/snapshots/rsearch.snap')
-rw-r--r--test/snapshots/rsearch.snap55
1 files changed, 31 insertions, 24 deletions
diff --git a/test/snapshots/rsearch.snap b/test/snapshots/rsearch.snap
index a83d27c4..d880e557 100644
--- a/test/snapshots/rsearch.snap
+++ b/test/snapshots/rsearch.snap
@@ -11,8 +11,6 @@ file code.txt run count_x now\nopen sub/dep.txt:3 here\ncount_x again\npick two
# the top of the body -- which moves every row this script clicks. What the
# verbs do is what is under test, not the announcement.
config Verbose off
-# its clicks and goldens were laid out by the pardes placement rule
-config Placement pardes
start 31 210 -n 1
wait 8000 code.txt
stable 700 20000
@@ -30,10 +28,11 @@ release right 6 9
wait 10000 count_x
stable 700 15000
snap opened
+# code.txt opens under the shell's text, its line 1 on screen row 8.
# right-CLICK the identifier `count_x` (line 1, the 'n' at col 15). It names no
# file, so the click searches for it: the results list both lines containing it.
-press right 15 4
-release right 15 4
+press right 15 8
+release right 15 8
# Locations stack the target under its line now: two rows, two waits.
wait 10000 code.txt:1:5-11
wait 10000 run count_x now
@@ -41,9 +40,9 @@ stable 700 15000
snap search
# right-SELECT `pick two` (line 4, sweep cols 8..15): a multi-word span passes
# through verbatim (the space is kept), unlike a click's single-word expansion.
-press right 8 7
-drag right 15 7
-release right 15 7
+press right 8 11
+drag right 15 11
+release right 15 11
wait 10000 code.txt:4:1-8
wait 10000 pick two words
stable 700 15000
@@ -51,45 +50,53 @@ snap select
# right-CLICK the path `sub/dep.txt:3` (line 2, col 18): isFileChar keeps / . :
# so the click expands the whole token and it RESOLVES — a look, not a search —
# opening dep.txt scrolled to line 3 (DEPTARGET). The "don't break paths" case.
-press right 18 5
-release right 18 5
+press right 18 8
+release right 18 8
wait 10000 DEPTARGET
stable 700 15000
snap path-open
# A click does not merely LIST the hits, it goes to one: this re-search of
-# `count_x` (line 1, col 15) also STEPS onto hit 1, so the cursor lands in the
-# match — line 1 col 5, not the column that was clicked.
-press right 15 4
-release right 15 4
+# `count_x` (line 3, col 12: acme sized code.txt to its four lines, and the
+# first search scrolled line 1 off) also STEPS onto hit 1, so the cursor lands
+# in the match, not where the click was.
+press right 12 9
+release right 12 9
stable 700 15000
snap step1
# ...and the same word clicked in its OTHER place (line 3, col 10) opens NO
# second +Search: the list is already armed on this pattern, so the click is
# `n`. Cursor moves to hit 2, line 3.
-press right 10 6
-release right 10 6
+press right 10 10
+release right 10 10
stable 700 15000
snap step2
# past the last hit the ring wraps: back to hit 1, line 1.
-press right 10 6
-release right 10 6
+press right 10 10
+release right 10 10
stable 700 15000
snap step3
+# acme sized code.txt to its four lines, and on so tight a pane a click on
+# line 4 scrolls it to keep its context rows: drag its last row (the resize
+# handle) down four rows first, so the rows below stay where they are clicked.
+press left 40 11
+drag left 40 15
+release left 40 15
+stable 700 15000
# A LEFT sweep over `pick two` (line 4, cols 8..15) and then a right CLICK
# INSIDE it: the click takes the whole selection — the search is for the
# two-word span (`4:1-8`), which the file-ish word expansion could never
# produce from the single word under the click.
-press left 8 7
-drag left 15 7
-release left 15 7
+press left 8 11
+drag left 15 11
+release left 15 11
stable 400 5000
-press right 11 7
-release right 11 7
+press right 11 11
+release right 11 11
stable 700 15000
snap selclick
# ...and a right click OUTSIDE the selection is the ordinary word click again:
# `words` (line 4, col 19), not the span left lying in the pane.
-press right 19 7
-release right 19 7
+press right 19 11
+release right 19 11
stable 700 15000
snap outside