summaryrefslogtreecommitdiff
path: root/test/replicas.zig
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-11-16 23:37:14 -0300
committerGabriel Schneider <[email protected]>2026-11-17 12:15:01 -0300
commite4fbb97a506ca2a4b469b6e2e13ecba6e516272c (patch)
tree9872f6ecfea4192c88e49e3439061a686bd6d9ed /test/replicas.zig
parentf25313ebb776aa4cca2dfbc49d3d3ff96dae161d (diff)
downloadpardes-e4fbb97a506ca2a4b469b6e2e13ecba6e516272c.tar.gz
pardes-e4fbb97a506ca2a4b469b6e2e13ecba6e516272c.zip
term: the terminal's own files move into src/term/ (terminal.zig, screen_state.zig, echo.zig, TerminalImages.zig), as they are: names and signatures kept, only the import paths change (theirs to ../, pardes.zig's, panes.zig's, tape.zig's, replica.zig's and Kind.zig's to term/), the comments that name them by path follow, and the embedded sources serve terminal.zig at src/term/terminal.zig; the first step of docs/next-terminal.md's Phase 0, a move, nothing else
Diffstat (limited to 'test/replicas.zig')
-rw-r--r--test/replicas.zig6
1 files changed, 3 insertions, 3 deletions
diff --git a/test/replicas.zig b/test/replicas.zig
index f50fb04f..56e08607 100644
--- a/test/replicas.zig
+++ b/test/replicas.zig
@@ -5,7 +5,7 @@
//! puts them all in one, where they clash at every key: a stress of
//! correctness, not a picture of a session.
//!
-//! Terminals cross as screen state (src/screen_state.zig): the session's
+//! Terminals cross as screen state (src/term/screen_state.zig): the session's
//! shell pane runs a full-screen program and then a `yes` flood (`--flood`
//! MB of it) while the clients type, its output stepped by the authority
//! and sent to each replica as deltas, once a frame and before any input
@@ -17,7 +17,7 @@
//! zig build replicas -Dplatform=tui -Doptimize=ReleaseFast -- --screen-state <dir>
//!
//! `--echo` types a corpus into a shell instead, with and without the
-//! predicted echo (src/echo.zig), and gates what it draws: below, at
+//! predicted echo (src/term/echo.zig), and gates what it draws: below, at
//! "predicted echo". `--screen-state` runs recorded pty streams through
//! screen_state's soak and measures its encoder: below, at screenState.
//!
@@ -534,7 +534,7 @@ fn sendUnit(q: *std.PriorityQueue(Msg, void, Msg.order), n: *u64, unit: []const
// plain echo, no marks). Each key's echo comes back 2 ms after the authority
// writes it, as a shell's. The client types at a typist's pace and in bursts;
// each of its frames (60 Hz, a phase of its own) is what its screen shows:
-// the predicted echo where it is drawn (src/echo.zig), the screen state
+// the predicted echo where it is drawn (src/term/echo.zig), the screen state
// under it. Per key the shell echoed at a prompt or in cat: the time from
// the key to its character on that screen, with prediction and without. Per
// key predicted: whether the authority's screen, right after its echo,