diff options
| author | user <user@clank> | 2026-08-15 23:41:12 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-15 23:41:12 +0200 |
| commit | c7498912d52b204e80086d2b6a93f27c7d87ebab (patch) | |
| tree | 806d0363b027bafcad184f4d0a3790320952a94c /src | |
| parent | sl0ppty: one family of marks for the frame's buttons (diff) | |
| download | slosh-c7498912d52b204e80086d2b6a93f27c7d87ebab.tar.gz slosh-c7498912d52b204e80086d2b6a93f27c7d87ebab.tar.xz slosh-c7498912d52b204e80086d2b6a93f27c7d87ebab.zip | |
sl0ppty: marks a font actually draws at cell size
▬ □ ✕ away, bigger, gone
▬ ■ ✕ ...and while it is already filling the tab
The boxed operators of the commit before this (⊞ ⊟ ⊡ ⊠) were one tidy
family and unreadable with it. They are *math* symbols, sized to sit
beside x and y in an equation, so at a terminal's cell size the interior
that carried the whole meaning -- the minus, the plus, the dot -- was two
or three pixels of it. Four identical smudges.
Geometric shapes and dingbats are drawn at full cell size, which is what
makes them readable at all, so legibility wins over uniformity here: four
different shapes, one verb each. Picking glyphs that fill their cell is
also the answer to the evenness that put plain ASCII here originally --
a glyph that does not fill its cell hands the slack to the gap beside it,
by an amount the font decides.
A bar for minimise rather than the obvious ▼, because the split guide
already owns all four triangles (◄ ► ▲ ▼) and the scroll indicator owns
▲ again. A glyph that means "split downward" on the border of a frame
cannot also mean "put this pane away" in its corner. Found by the guide's
own test failing on the first attempt, which is exactly what that test is
for -- and the reason it caught a UI collision rather than a typo is that
it asserts only *one* arrow is on screen at a time.
Widths checked in a real frame again: the rule still closes on its
corner, each button is still measured rather than booked, and the hits
land on the glyphs.
Diffstat (limited to 'src')
| -rw-r--r-- | src/config.c | 35 |
1 files changed, 25 insertions, 10 deletions
diff --git a/src/config.c b/src/config.c index 421a1cd..1d29c06 100644 --- a/src/config.c +++ b/src/config.c @@ -347,16 +347,31 @@ void config_defaults(config_t *c) { c->hints = true; c->version_banner = true; c->pane_buttons = true; - /* One family, four interiors: minus, plus, dot, times. The lesson that put - * ASCII here in the first place was about *evenness* -- a glyph that does not - * fill its own cell hands the slack to the gap beside it -- and four copies of - * the same box answer that better than four unrelated glyphs did, while still - * saying which verb is which. Single width, and not emoji: many terminals - * draw those two columns wide while chrome here is booked as one. */ - snprintf(c->zoom_mark, sizeof c->zoom_mark, "\u229e"); /* ⊞ fill the tab */ - snprintf(c->zoom_on_mark, sizeof c->zoom_on_mark, "\u22a1"); /* ⊡ and put it back */ - snprintf(c->close_mark, sizeof c->close_mark, "\u22a0"); /* ⊠ close */ - snprintf(c->min_mark, sizeof c->min_mark, "\u229f"); /* ⊟ into the strip */ + /* Geometric shapes and a dingbat, because those are the blocks a font draws + * at full cell size. The boxed operators these replaced (⊞ ⊟ ⊡ ⊠) were one + * tidy family and unreadable with it: they are *math* symbols, sized to sit + * beside x and y in an equation, so at a terminal's cell size the interior + * that carried the whole meaning was two or three pixels of it. + * + * Legibility beats uniformity here, so these are deliberately different + * shapes: a bar for away, an outline for "make it fill the tab", the same + * outline filled in for "it is filling it", a cross for gone. The evenness + * problem that put ASCII here originally is answered by picking glyphs that + * fill their cell rather than by picking one family -- a glyph that does not + * hands the slack to the gap beside it, by an amount the font decides. + * + * A *bar* for minimise rather than the obvious ▼, because the split guide + * already owns all four triangles (◄ ► ▲ ▼) and the scroll indicator owns ▲ + * again: a glyph that means "split downward" on the border of a frame cannot + * also mean "put this pane away" in its corner. Found by the guide's own test + * failing, which is what that test is for. + * + * Single width, and not emoji: many terminals draw those two columns wide + * while chrome here is booked as one. */ + snprintf(c->zoom_mark, sizeof c->zoom_mark, "\u25a1"); /* □ fill the tab */ + snprintf(c->zoom_on_mark, sizeof c->zoom_on_mark, "\u25a0"); /* ■ ...and back */ + snprintf(c->close_mark, sizeof c->close_mark, "\u2715"); /* ✕ close */ + snprintf(c->min_mark, sizeof c->min_mark, "\u25ac"); /* ▬ into the strip */ snprintf(c->newtab_mark, sizeof c->newtab_mark, "+"); c->bell_indicator = true; snprintf(c->bell_mark, sizeof c->bell_mark, "\u2022"); |
