diff options
| author | user <user@clank> | 2026-08-14 20:28:30 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-14 20:28:30 +0200 |
| commit | 5cdbca2c8a896fd0e25cfc03aa44ba0143d2d31b (patch) | |
| tree | 1f5bb282eb798164816383eabb8ca39d399ec29c /config | |
| parent | sl0ppty: halve the padding between the frame's buttons (diff) | |
| download | slosh-5cdbca2c8a896fd0e25cfc03aa44ba0143d2d31b.tar.gz slosh-5cdbca2c8a896fd0e25cfc03aa44ba0143d2d31b.tar.xz slosh-5cdbca2c8a896fd0e25cfc03aa44ba0143d2d31b.zip | |
sl0ppty: plain ASCII for the frame's buttons
_ for minimise, # for zoom, * for the way back, x for close.
Box-drawing and block characters were each tried and each looked unevenly
spaced, which is the answer: the cells are even every time, and what differs is
how much of its own cell a glyph fills. That is a property of the font, not
something to be fixed from here, and single-width ASCII of a similar weight is
the way to stop asking the question.
The measurement stays, so a mark is still yours to change and may be more than
one character. The config note now says what the three attempts established
rather than what I expected each time.
Diffstat (limited to 'config')
| -rw-r--r-- | config/config.kdl | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/config/config.kdl b/config/config.kdl index e89a8ac..689c7c9 100644 --- a/config/config.kdl +++ b/config/config.kdl @@ -53,15 +53,18 @@ title_inset 2 // the setting is about the affordance and not the verb. pane_buttons true -// The buttons are evenly spaced whatever is in them, but how even they *look* -// depends on the glyphs: a light character floating in a mostly-empty cell -// donates that space to the gap beside it. Emoji are worse -- many terminals -// draw them two columns wide while chrome here is booked as one -- so avoid -// those. A mark may be more than one character; the button is measured rather -// than assumed, so "[]" and "][" work too if you prefer them. Put the character itself +// Plain single-width ASCII, after box-drawing and block characters were each +// tried and each looked unevenly spaced: the cells are even, but a glyph that +// does not fill its own cell hands that space to the gap beside it, and how +// much it hands over depends on the font. ASCII of a similar weight sidesteps +// the question. Emoji are the worst case -- many terminals draw them two +// columns wide while chrome here is booked as one. +// +// A mark may be more than one character; the button is measured rather than +// assumed, so "[]" and "][" work if you prefer them. Put the character itself // here; this file has no \u escape. -zoom_mark "□" -zoom_on_mark "▣" +zoom_mark "#" +zoom_on_mark "*" close_mark "x" min_mark "_" |
