aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authoruser <user@clank>2026-08-14 19:48:30 +0200
committeruser <user@clank>2026-08-14 19:48:30 +0200
commite021e0d05926fbaae2b53edaf256fdd7b31aff1d (patch)
treee841ac08f4b5a241d4013fcfd0a6207eb78e4f43 /README.md
parentsl0ppty: zoom a pane, and give the frame buttons for it (diff)
downloadslosh-e021e0d05926fbaae2b53edaf256fdd7b31aff1d.tar.gz
slosh-e021e0d05926fbaae2b53edaf256fdd7b31aff1d.tar.xz
slosh-e021e0d05926fbaae2b53edaf256fdd7b31aff1d.zip
sl0ppty: minimise a pane into a strip along the bottom
A pane can be put away: it leaves the layout, becomes one row at the bottom of the tab, and keeps running. The panes it leaves behind take the space back. Clicking its row brings it back. Minimised is intent, so it sits beside the weight on the node rather than with the rect and the collapsed flag — and layout_node has to be careful not to clear it the way it clears those, or every frame would undo it. That is the only sharp edge in the whole thing and it has a comment. Everything else fell out of rules that already existed. A split divides among the children that still want space, so a split with one live child is that child, exactly as a split with one child already was. A minimised leaf returns from layout_node before its rect is touched, which also skips the floor check — a pane that is one row by request is not a pane that failed to fit. And the row itself is drawn by the same code as a collapsed header, because it is the same thing: a pane you can see the name of and click. Restoring is not a verb. A focused pane is never minimised, checked once a frame, so every route that ends with the pane focused restores it — clicking the row, the control API, and anything added later that moves focus without knowing minimising exists. In a tab that has flattened into a list, minimising has no effect at all, which is what was asked for and also what falls out: every pane down there is already a row, so there is no second thing for it to be. The strip is not reserved when it would leave too little above it to be worth looking at; the tab flattens instead, and arrives at the same place. Minimising the last visible pane is refused with a toast. A tab showing nothing has no way back that can be discovered from the tab, and it is not a state worth being able to reach by accident. The frame's third button costs another three columns, which is why they are drawn right to left and stop when they run out: a narrow pane keeps close and zoom, and loses minimise first.
Diffstat (limited to 'README.md')
-rw-r--r--README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index ab548b5..51b51c5 100644
--- a/README.md
+++ b/README.md
@@ -83,6 +83,12 @@ fills the tab until you put it back; the other panes keep running, they are
just not drawn. `×` beside it closes the pane. `pane_buttons false` takes both
buttons off without touching the keybindings.
+**Minimise a pane** with `C-a m` or the `–` button and it leaves the layout for
+a strip along the bottom, one row each, still running — the panes it leaves
+behind take the space back. Click its row to bring it back. Once a tab is too
+small and has flattened into a list, being minimised means nothing: every pane
+is a row down there already.
+
**Select to copy.** Drag over text and release: it is on your clipboard, sent
to your terminal as OSC 52 so it works over ssh. Middle click pastes it back,
the way a primary selection behaves everywhere else. A program in a pane can