aboutsummaryrefslogtreecommitdiffstats
path: root/docs/scripting.md
diff options
context:
space:
mode:
authoruser <user@clank>2026-09-22 15:38:08 +0200
committeruser <user@clank>2026-09-22 15:38:08 +0200
commit1cbfb4474ca31c61254be8d5f3ec046967bd1ff3 (patch)
tree3e8184674e330ce24ebef23dd13594fa38f45fa2 /docs/scripting.md
parentsidebar: room for the spinner, by default (tab_bar_padding 0 1 0 2) (diff)
downloadslosh-1cbfb4474ca31c61254be8d5f3ec046967bd1ff3.tar.gz
slosh-1cbfb4474ca31c61254be8d5f3ec046967bd1ff3.tar.xz
slosh-1cbfb4474ca31c61254be8d5f3ec046967bd1ff3.zip
theme: the busy spinner is its own colour (tab_status_spinner)
It was drawn in tab_status_busy, the colour of the words it sits beside, which made one decision out of two. The words have to stay readable at a glance and a mark does not: a theme may well want the glyph loud and the text calm -- or the text in the accent and the mark a quiet dot -- and with one entry neither is available without moving both. Unset it follows tab_status_busy, derived after it and from whatever that resolved to, named or derived, so nothing changes for anyone who does not ask and no theme in contrib needs a line. `--dump-theme` writes both, like every other colour the compositor draws.
Diffstat (limited to 'docs/scripting.md')
-rw-r--r--docs/scripting.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/scripting.md b/docs/scripting.md
index 9971bc5..8fff400 100644
--- a/docs/scripting.md
+++ b/docs/scripting.md
@@ -115,7 +115,8 @@ keep it current and `clear` it when the work is done.
of its own rather than a field of `status`, because a status is the *whole*
payload after the verb — `status;a;b;c` is the text `a;b;c` — so anything added
to that line would change what every sender already means. In a sidebar a busy
-status gets the spinner (`busy_mark`) and `tab_status_busy`, which is how
+status gets the spinner (`busy_mark`, coloured `tab_status_spinner`) and
+`tab_status_busy`, which is how
"working" and "done" tell themselves apart from another tab without reading the
words. Anything but `0`, `false`, `no` or `off` turns it on; `clear` turns it
off along with the text, and so does the program exiting — a status left behind