max / alloy

stack: say that no multiplexer ships either The "panes are sway's job" bullet said what the terminal does not do and not what the image does not have. tmux and zellij are not installed, which makes it a stack position rather than an omission, and shop's README was pointing users at them.

Author: Max Johnson <me@maxj.phd> · 2026-07-25 13:23 UTC

Signed with PGP, not checked

Commit: e9cdfaea6cce9e4368485358d6bf39771dae58ef

Parent: fc7e9e0

1 file changed, +1 insertion, -1 deletion

M docs/STACK.md +1 -1

			@@ -104,7 +104,7 @@
104	104		Secondary alignments:
105	105		- TOML config. No scripting language dependency, consistent with Alloy's rejection of Lua/yuck/similar config surfaces elsewhere in the stack.
106	106		- Design-forward posture. Rio treats the terminal as a displayed surface, not just a fast text renderer. That matches Alloy's design-system stance.
107		-	- No multiplexing. Tabs, splits, panes are sway's job. A terminal that also tiles is duplicated budget.
	107	+	- No multiplexing. Tabs, splits, panes are sway's job. A terminal that also tiles is duplicated budget. Alloy therefore ships no multiplexer either: tmux and zellij are not in the image, and a terminal's own docs should not send an Alloy user looking for them. A window is a window, and `Mod+H/J/K/L` moves between them.
108	108
109	109		yazi runs with kitty graphics under rio, not sixel. Both work in rio; kitty is the modern protocol, sixel is the compat path. Yazi picks the graphics protocol at runtime by detecting terminal capability from `TERM` / `TERM_PROGRAM`, so the config work is small:
110	110