From 77c7d0bae3b69dc6fccc7cfea7d30aabc1543409 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Mon, 28 Sep 2026 13:35:24 -0300 Subject: With no frontend attached, a detached session's messages go after MessageLinger A message lingers until input dismisses it, and a detached session with nobody attached has no input: its messages, and /screen, kept what was said long ago. The session now marks the core unattended while no client is attached, and the core drops a pane's messages once the newest has been up MessageLinger on the clock, checked as it is stepped or served. A pane's older lines go with its newest rather than each on its own clock; the render pipeline's clock is the place for that. Co-Authored-By: Claude Opus 5.5 --- docs/detached.md | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs/detached.md') diff --git a/docs/detached.md b/docs/detached.md index 2111e3dc..17c225f2 100644 --- a/docs/detached.md +++ b/docs/detached.md @@ -17,6 +17,11 @@ Inside an editor, `Attach work` (`SPC s a`) switches the current window to that session. `Detach` (`SPC s D`) closes only that frontend. It does not turn a local editor into a detached session. +A message stays until the next key or click dismisses it. With no frontend +attached there is none to come, so a detached session drops each pane's +messages once the newest has been up `MessageLinger` on the clock, as the +editor is stepped or served over 9P; /screen then shows what is current. + ## Files and transport The frontend socket is `pardes-detached-.sock` under -- cgit v1.3