aboutsummaryrefslogtreecommitdiffstats
path: root/web
diff options
context:
space:
mode:
authoruser <user@clank>2026-09-10 16:32:10 +0200
committeruser <user@clank>2026-09-10 16:32:10 +0200
commita2d08f4876226446c0052f033e8afea2f2ffbbf1 (patch)
treeac77189b9c928939202adca4a43298730bccd8d2 /web
parentsidebar: the new-tab button says what it is, given a row to say it on (diff)
downloadslosh-a2d08f4876226446c0052f033e8afea2f2ffbbf1.tar.gz
slosh-a2d08f4876226446c0052f033e8afea2f2ffbbf1.tar.xz
slosh-a2d08f4876226446c0052f033e8afea2f2ffbbf1.zip
sidebar: statuses wear italic instead of an indent, and can wear colour
Three columns of indent is a fifth of a sixteen-column sidebar, spent saying 'this belongs to the row above'. The slant says it in none: a status now starts in the same column its tab's name starts in, and is set in italic. That also survives the monochrome themes in contrib, where a colour-only distinction would have had nothing to spend. tab_status_fg / tab_status_bg are there for themes that do have colour to spend. The fg follows tab_count when a theme does not name it -- the same declared/derived split apply_scrolled makes -- so the six themes in contrib get coherent status rows without a line added to any of them. The bg is unset by default, because a band is opt-in and 'none' is what a translucent terminal wants; the row is padded so a band that *is* set covers the row rather than the words on it. Two things fell out. The padding loop existed three times and is now pad_cells. And cb_color wrote #000000 for an unset colour, so quietly pinned attach_bg -- 'gray ink on the terminal's own background', says its comment -- to a black band. Unset colours are now written commented out, the same trick the states block uses for what it wants re-derived rather than pinned.
Diffstat (limited to 'web')
-rw-r--r--web/index.html9
1 files changed, 6 insertions, 3 deletions
diff --git a/web/index.html b/web/index.html
index 9dacd72..e9ac8ea 100644
--- a/web/index.html
+++ b/web/index.html
@@ -237,12 +237,15 @@ Server = https://slosh.foo/arch/$arch</code></pre>
<div class="cmd">
<pre><code><span class="prompt">$</span> git clone https://github.com/sl0p-foo/slosh.git &amp;&amp; cd slosh
<span class="prompt">$</span> make vendor <span class="c"># the vendored terminal core, once</span>
-<span class="prompt">$</span> make <span class="c"># about a second</span>
-<span class="prompt">$</span> sudo install build/slosh /usr/local/bin/</code></pre>
+<span class="prompt">$</span> make all <span class="c"># about a second</span>
+<span class="prompt">$</span> sudo make install <span class="c"># or: make install PREFIX=$HOME/.local</span></code></pre>
</div>
<p class="aside">Needs <a href="https://ziglang.org">zig</a> 0.16 and
nothing else: no cmake, no autotools, no libraries. The result is one
- static binary. Windows cross-compilation is
+ static binary. Bare <code>make</code> prints the target list;
+ <code>make&nbsp;all</code> is the build, and <code>make&nbsp;install</code>
+ puts the binary in <code>$PREFIX/bin</code> along with the manpages and
+ the example configuration. Windows cross-compilation is
<code>make&nbsp;-f&nbsp;Makefile.windows</code>;
<a href="docs/windows.html">the details</a>.</p>
</div>