summaryrefslogtreecommitdiff
path: root/test/snapshots/nested.snap
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-06 18:11:36 -0300
committerGabriel Schneider <[email protected]>2026-09-07 13:59:12 -0300
commit60367d8fe23f6af98ec28e3cf6c2094dfe332df0 (patch)
tree310fc734173cf771881f4691c71909135fadde97 /test/snapshots/nested.snap
parentfa82cac885cb4738fe36d1e49b4749b5a3e31a4a (diff)
downloadpardes-60367d8fe23f6af98ec28e3cf6c2094dfe332df0.tar.gz
pardes-60367d8fe23f6af98ec28e3cf6c2094dfe332df0.zip
Refactor panes and filesystem; replace FUSE with 9P
Consolidate pane, layout, memory and host code. Serve 9P by default over Unix sockets, with runtime mounts and optional TCP/QUIC transports. Remove FUSE and obsolete proof-of-concept examples. Fix highlighting and terminal-history performance, expand differential and stress-test infrastructure, sort navigation results while preserving the next occurrence, add syntax-colored Braille minimaps, remove SPC-k, and document 9P interaction as a repository skill.
Diffstat (limited to 'test/snapshots/nested.snap')
-rw-r--r--test/snapshots/nested.snap21
1 files changed, 0 insertions, 21 deletions
diff --git a/test/snapshots/nested.snap b/test/snapshots/nested.snap
index 0beeabf8..790b9b0c 100644
--- a/test/snapshots/nested.snap
+++ b/test/snapshots/nested.snap
@@ -1,34 +1,14 @@
-# a pardes launched INSIDE a pardes hands its argument to the outer one.
-#
-# No harness support is needed to get a genuinely nested launch: a pane
-# shell's parent IS the app under test, so `$(readlink /proc/$PPID/exe)` in a
-# pane is this exact binary, and running it from there makes a real
-# descendant — the same process tree a person typing `pardes foo.txt` in a
-# pane produces. Each arm gets its own `start` so the Look never has to be
-# aimed at a pane a previous arm moved.
-#
-# What discriminates is the GOLDEN GRID, not the `wait` below it: a nested
-# pardes that opened its own UI in the pane would show the same file, so the
-# content wait passes either way. The layout is what differs — an outer file
-# pane beside the shell versus a whole second topbar inside it — and the
-# `cursor=` on the first arm's header moves the moment that changes.
-#
-# Long waits on purpose: this forks and execs a whole second pardes.
dirmk nestdir
file nestdir/inside-nested.txt marker
file nested.txt hello-from-nested\nsecond-nested-line\n
-# --- a FILE argument: a file pane appears in the OUTER instance ---
start 30 100
wait 8000 $
stable 700 20000
text $(readlink /proc/$PPID/exe) nested.txt
key enter
-# the CONTENT, not the border: the shell only ever echoed the file's NAME
-# (see above for why the grid, not this line, is the real assertion)
wait 15000 hello-from-nested
stable 700 20000
snap file-arg
-# --- no argument: the spicy message, in the pane, and no second UI ---
start 30 100
wait 8000 $
stable 700 20000
@@ -37,7 +17,6 @@ key enter
wait 15000 already inside pardes
stable 700 20000
snap no-arg
-# --- a DIRECTORY argument: a shell there, greeted with ls ---
start 30 100
wait 8000 $
stable 700 20000