feat: theme pi and omp from the same tinty scheme as ghostty and tmux - #6
Open
body-clock wants to merge 1 commit into
Open
body-clock wants to merge 1 commit into
body-clock wants to merge 1 commit into
Conversation
Tinty already owns the scheme for ghostty and tmux, but pi and omp were themed by hand, so a scheme change left them behind. Both are now tinty items and get their theme file regenerated from the same base16/base24 scheme: - tinted-pi (github.com/body-clock/tinted-pi) -> ~/.pi/agent/themes/tinted.json - tinted-omp (local plugin checkout) -> ~/.omp/agent/themes/tinted.json Also: - ghostty hook: drop the `>/dev/null` on the reload, so a failing reload.scpt says why instead of silently leaving the old theme on screen. - bootstrap.sh: `tinty install` + `tinty apply base16-tarot` right after stowing. Ghostty's config points at ~/.config/ghostty/themes/tinted-theming, a generated file that does not exist yet on a fresh machine. Known limitation: the omp item points at ~/code/tinted-omp, which is a local checkout with no git remote, so `tinty install` cannot fetch it on another machine. It needs to be published (or pointed at a URL) before bootstrap can be relied on there.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Tinty already owns the scheme for ghostty and tmux, but pi and omp were themed by hand, so a scheme change left them behind. Both are now tinty items and get a theme file regenerated from the same base16/base24 scheme:
tinted-pi(github.com/body-clock/tinted-pi)~/.pi/agent/themes/tinted.jsontinted-omp(local plugin checkout)~/.omp/agent/themes/tinted.jsonAlso:
>/dev/nullon the reload, so a failingreload.scptsays why instead of silently leaving the old theme on screen.bootstrap.sh:tinty install+tinty apply base16-tarotright after stowing. Ghostty's config points at~/.config/ghostty/themes/tinted-theming, a generated file that does not exist yet on a fresh machine.Verification
config.tomlparses as TOML; the four items resolve in order (tinted-ghostty, tinted-tmux, tinted-pi, tinted-omp).body-clock/tinted-piexists (private).Review notes
~/code/tinted-omphas no git remote (git remote -vis empty; local commitsf6d16d7,31ec3e0), sotinty installcannot fetch it on another machine and the bootstrap step will not reproduce the omp theme there. Publishing it, or pointing the item at a URL, would close that gap.%fwhile the omp item copies$TINTY_THEME_FILE_PATHfor the same thing. Both work withshell = "zsh -c '{}'"; is the difference deliberate?Overlap with an open PR
Open PR #2 (
feat/tinted-fzf-integration, 2026-08-13) already registers the sametinted-piitem, byte for byte, inconfig.tomlnext to its fzf/tuicr items, and it also changesshellat the top of that file. Both PRs append at the end ofconfig.toml, so the second one to land needs a rebase and the pi item must not be registered twice. Nothing here depends on #2 — the omp item, the ghostty hook change and the bootstrap init step are all new — but they share the file.