abe98fa0

docs: an exited tile leaves the wall without a word

a73x 2026-08-28 19:53

Commit message

docs: an exited tile leaves the wall without a word

README.md

Old		New
@@ -120,11 +120,11 @@ and empty, and the next `mux HOST` is born into it — so emptying a machine
120	costs you nothing but the shell you meant to end. Ending the daemon itself	120	costs you nothing but the shell you meant to end. Ending the daemon itself
121	is `muxd stop`.	121	is `muxd stop`.
122		122
123	A session whose shell exits takes its tile off the wall, with the tile that	123	A session whose shell exits takes its tile off the wall. On a terminal the
124	ended saying so. On a terminal the LAST tile's exit leaves you on the empty	124	LAST tile's exit leaves you on the empty wall with the picker over it, not
125	wall with the picker over it, not back in your shell: `Ctrl-\` `d` is how	125	back in your shell: `Ctrl-\` `d` is how you leave. A piped `mux` has no wall
126	you leave. A piped `mux` has no wall to leave you on, so it exits with that	126	to leave you on, so it exits with that shell's code — `mux` stays something
127	shell's code — `mux` stays something you can put in a script.	127	you can put in a script.
128		128
129	The wheel goes to whatever is in front of it. At a shell prompt it moves	129	The wheel goes to whatever is in front of it. At a shell prompt it moves
130	mux's scrollback, three rows a notch. In a full-screen application that did	130	mux's scrollback, three rows a notch. In a full-screen application that did