summaryrefslogtreecommitdiff
path: root/test/snapshots/jumps.snap
diff options
context:
space:
mode:
Diffstat (limited to 'test/snapshots/jumps.snap')
-rw-r--r--test/snapshots/jumps.snap50
1 files changed, 36 insertions, 14 deletions
diff --git a/test/snapshots/jumps.snap b/test/snapshots/jumps.snap
index 1e2a9075..db131bd4 100644
--- a/test/snapshots/jumps.snap
+++ b/test/snapshots/jumps.snap
@@ -64,36 +64,58 @@ snap last-back
key space j l
stable 700 15000
snap jumplist
-# n/N step the rows and look them, exactly as they do a +Search: the stepped
-# row is selected in the buffer (snapstyle) and the pane it names follows.
-# Row 1 is the shell (no path, so `@pN`), row 2 the file at line 1, row 4 the
-# file at line 100 — so the body visibly rides the list.
+# n/N select the next/prev look-able span and Enter looks it, exactly as they
+# do a +Search: the stepped span is selected in the buffer (snapstyle) and the
+# Enter after it moves the pane the row names. Row 1 is the shell (no path, so
+# `@pN`), row 2 the file at line 1, row 4 the file at line 100 — so the body
+# visibly rides the list.
#
-# ponytail: stepping onto an `@pN` row selects it but does NOT focus that pane —
-# the cursor stays where it was, which is why step1-shell's header is still the
-# file's. Only rows with a PATH move focus. Nothing tested this before, because
-# until the swap above the shell never survived on the stack to be listed at
-# all. Fix belongs in the location-list step, next to the path case.
+# SPANS, not rows, and this buffer is the one place in the suite where the two
+# differ: an `@pN` row's trailing text is the pane's DIRECTORY, which is a
+# look-able word of its own, so row 1 and row 3 each hold TWO stops and
+# reaching the next row takes two steps. A file row's text is its content line
+# (`line 1`), which resolves to nothing, so those hold one. Stepping words
+# rather than rows is what makes the walk the same motion in a results buffer
+# and in the middle of a paragraph, and this is the price of that.
+#
+# An `@pN` row moves focus like any other, which it did not use to: the STEP
+# only selects now, and the look Enter runs goes to the pane by the same route
+# a path takes.
key n
+key enter
stable 700 15000
snap step1-shell
snapstyle step1-shell
+# past the directory on row 1, then onto row 2
+key n
+stable 400 5000
key n
+key enter
stable 700 15000
snap step2-file
+# row 3 is the shell again, both its spans, and then row 4
key n
-stable 700 15000
+stable 400 5000
key n
+stable 400 5000
+key n
+key enter
stable 700 15000
snap step4-line100
+# N is the exact inverse: the same two spans of row 3 in the other order, so
+# two presses land back on its location and Enter follows it to the shell
+key N
+stable 400 5000
key N
+key enter
stable 700 15000
snap step-back
# and an ordinary LOOK on a row goes there too — the leading word IS a
# location, so the right-click look resolves it like any other path. Row 4
-# again, this time by clicking it: the buffer's four rows are the last four
-# screen rows, so row 4 is the bottom one.
-press right 16 30
-release right 16 30
+# again, this time by clicking it: the walk above scrolled the list by one, so
+# the last four screen rows are its rows 2 through 5 and row 4 is the second
+# from the bottom.
+press right 16 29
+release right 16 29
stable 700 15000
snap look-row