From f316b46caea6ecf947989114c37af8288b37dbf5 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Sat, 7 Nov 2026 00:27:21 -0300 Subject: themes: a theme may colour the tagline (the workspace row) on its own, tagline_bg and tagline_fg, an editor's status bar, resolved to the tag's colours without them (ChromeTheme); dark_plus takes VS Code's statusBar.background #007acc with white text, cited; the chrome floors test holds the pair to 4.5:1 and the default to the tag's; the theme and themesel snapshots move by that row Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge --- src/CHANGELOG.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'src/CHANGELOG.md') diff --git a/src/CHANGELOG.md b/src/CHANGELOG.md index 8107f920..8bb5216c 100644 --- a/src/CHANGELOG.md +++ b/src/CHANGELOG.md @@ -2,6 +2,10 @@ ## Unreleased +- A theme may give the tagline (the workspace row) colours of its own, + `tagline_bg` and `tagline_fg`, an editor's status bar; dark_plus has VS + Code's blue. Without them the row keeps the tag's colours, as before. + - MuPDF and FreeType are lazy: a fresh checkout's `zig build -Dplatform=tui` fetches neither; `-Dpdf` fetches MuPDF the first time (and is on by itself after), and without it the PDF steps say so. -- cgit v1.3