diff options
Diffstat (limited to 'test/replicas.zig')
| -rw-r--r-- | test/replicas.zig | 6 |
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, |
