slosh.git/docs, branch v0.1.6an opinionated terminal multiplexer in C with programmable pane chromehttps://git.sl0p.foo/slosh.git/atom/docs?h=v0.1.62026-09-02T14:24:41Zpty: install the terminfo entry implicitly when it is missing everywhere2026-09-02T14:24:41Zuseruser@clank2026-09-02T14:24:41Zurn:sha1:c58a875ef3bcb464cdbea72bdbd0a874b6f93729
The lookup miss now writes the embedded entry to ~/.terminfo and
uses it, so a bare box gets the full TERM with no step at all. An
entry that exists anywhere is respected -- possibly newer, certainly
somebody's -- and a HOME that cannot be written leaves the
xterm-256color fallback standing. --install-terminfo stays as the
by-hand spelling; the writer moved to pty.c where the panes are.
slosh --install-terminfo: the binary carries its own terminfo entry2026-09-02T14:22:03Zuseruser@clank2026-09-02T14:22:03Zurn:sha1:f9986df0da09cc692e168e33ef9ccfab5b9d2faf
The xterm-256color fallback works everywhere; the real entry is
better, and a tarball user on a bare box had no easy way to get it.
The entry is generated from the vendored tree (contrib/terminfo, so
it describes the terminal core we actually ship), compiled with tic,
embedded as bytes, and written to ~/.terminfo under every name it
answers to, letter and Darwin-hashed layouts both. No root, no
package, no conflict with a ghostty installed later. Proven end to
end in a mount namespace: bare box falls back, installs, and the
next pane says xterm-ghostty.
pty: fall back to xterm-256color where xterm-ghostty has no terminfo2026-09-02T14:15:55Zuseruser@clank2026-09-02T14:15:55Zurn:sha1:07194e139fbb90cb946be4d1e50e4937dab1ce04
TERM=xterm-ghostty was unconditional, but the entry ships with
ghostty and a machine that has never seen ghostty has ncurses'
database and nothing else. There, nano exits the moment it opens
(C-a e flashing a pane) and a shell that cannot look up kbs guesses
at backspace. The entry is now looked up the way curses would --
TERMINFO, ~/.terminfo, TERMINFO_DIRS, the system dirs, letter and
Darwin-hashed layouts -- and when absent, panes get xterm-256color,
which every ncurses database carries. Verified both ways with a
mount namespace hiding the database.
docs: sweep the em dashes2026-09-02T13:17:01Zuseruser@clank2026-09-02T13:17:01Zurn:sha1:bce260f8f2b63c4e99d416ba483ff7d14b4bb1de
Parentheses for the asides, colons for the explanations, commas and
semicolons for the joins, (none) for the empty table cells. Same
treatment the landing page got, across README, docs/, and both
manpages (\(em included).
attach tag: just the count, in theme colours2026-09-02T13:09:36Zuseruser@clank2026-09-02T13:09:36Zurn:sha1:cafa48e0a7e1eb48a783bfde6862c5fd82c7aede
The +x+y offset goes -- 'N clients' says the thing that matters. The
inverse-video chip goes with it: the tag now draws in attach_fg /
attach_bg from the theme, defaulting to gray ink on the terminal's
own background. Standing information, not an announcement.
multi-attach: say who else is watching, and where you are2026-09-02T13:03:53Zuseruser@clank2026-09-02T13:03:53Zurn:sha1:1a3ba183ae8f2613cae847c8f6460782512acc40
A small tag in each client's own top-right corner when several
terminals share the session: the viewer count, and on a view that is
a crop being panned by somebody else's cursor, the crop's offset into
the shared screen ("2 clients +12+4") -- which is exactly the moment
a screen moving on its own needs explaining. Stamped per client after
projection, because every terminal has its own count of others and
its own offset; the shared status bar is composed once and can be
cropped out of a panned view anyway. attach_indicator false hides
it.
multi-attach: the config knobs2026-09-02T12:57:13Zuseruser@clank2026-09-02T12:57:13Zurn:sha1:d698946464f25a0eb43730ffad15656f3247f56b
The patch made shared attach unconditional; these make it a policy.
multi_attach false restores the classic displacing attach
(EXIT_REPLACED, which old clients already understand). size_follows
picks whose size the shared screen takes: active (the patch's rule),
smallest (the tmux rule: filler, never a crop), or largest. The size
fold lives in apply_canvas, so any attach, resize or departure can
move the canvas under the folding policies -- including a non-active
client leaving, which under smallest may have been the very client
holding the floor down. A config reload re-applies both knobs to the
running session.
Add competitive multiplayer support.2026-09-02T12:51:02ZIngmar Steeniksteen@gmail.com2026-08-31T12:43:32Zurn:sha1:29061a4aca5e3d645c0e23b885342036ac48f97b
Last input wins, canvas size is adjusted to active connection.
shaders: remove the .so plugin loader2026-09-02T12:43:09Zuseruser@clank2026-09-02T12:43:09Zurn:sha1:18d1aef0f9bf4620135fd9f77f26683e6f2f8c00
The static musl release builds cannot dlopen -- musl compiles it out
-- so loadable shader plugins were a feature most shipped binaries
could not use. Nothing we ship used it either: every shader in
contrib/shaders is an expression. Gone: the dlopen/glob loader in
shader.c, shader_dir in the config, the plugin ABI table and entry
macro, the Windows dl*/glob shims that existed only for it, the
contrib/shader-plugin skeleton, its tests, and every doc mention.
shader_abi.h stays as the shader model (cell_t, shade_ctx_t,
shader_t) with a note about what it used to be.
public links: point at github.com/sl0p-foo/slosh instead of cgit2026-09-02T12:07:37Zuseruser@clank2026-09-02T12:07:37Zurn:sha1:597135f7851e83e31d99fc9c97fbb087c3df4fce
GitHub is the public interaction point now. The formula and PKGBUILD
fetch GitHub's /archive/ tarballs (same git-archive bytes, per-ref
stable); the PKGBUILD is bumped to 0.1.2 while at it, and its cd's
drop the v -- GitHub tag archives extract to slosh-X.Y.Z/. The cgit
remote stays for pushing; only published URLs change.