afada8b8

docs: the wall's empty-host paragraph said muxd exits on empty

a73x 2026-08-28 19:53

Commit message

docs: the wall's empty-host paragraph said muxd exits on empty

It does not any more, and an empty host is the ordinary local case rather
than a remote curiosity — the picker's whole reason to exist.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

README.md

Old		New
@@ -390,12 +390,12 @@ daemon is the exception that is started rather than waited for: a listed
390	local `--sock <default>` that nothing is serving is started for you, because	390	local `--sock <default>` that nothing is serving is started for you, because
391	it dies on every reboot while its line lives on.	391	it dies on every reboot while its line lives on.
392		392
393	A host that answers with an EMPTY list contributes nothing either. You will	393	A host that answers with an EMPTY list contributes nothing either, and that
394	not see that from your own machine — `muxd` exits when its last session	394	is an ordinary state rather than a remote curiosity: a daemon lives until
395	ends, so a local daemon that answers at all has at least session `0` — but a	395	`muxd stop`, so one whose last session you ended sits there with nothing to
396	remote daemon something else is holding open can sit there with nothing to	396	show until someone is born into it again. A wall on which no host has a live
397	show. A wall on which no host has a live session is empty, and says so on	397	session is empty, and says so on one line rather than showing a blank screen
398	one line rather than showing a blank screen that reads as hung.	398	that reads as hung.
399		399
400	A daemon too old to be asked shows nothing too. Listing a daemon's live	400	A daemon too old to be asked shows nothing too. Listing a daemon's live
401	sessions is a new question on the wire, and a daemon from before this change	401	sessions is a new question on the wire, and a daemon from before this change