Skip to content

feat: extend tinty theming to fzf, pi, and tuicr - #2

Open
body-clock wants to merge 2 commits into
mainfrom
feat/tinted-fzf-integration
Open

feat: extend tinty theming to fzf, pi, and tuicr#2
body-clock wants to merge 2 commits into
mainfrom
feat/tinted-fzf-integration

Conversation

@body-clock

Copy link
Copy Markdown
Owner

Summary

Switching a tinty scheme now restyles the fzf picker, the pi coding agent, and the tuicr code-review TUI, on top of the terminal and tmux. Hook scripts read tinty's current scheme and its base16/base24 palette, then emit each tool's native theme file so everything tracks the active scheme automatically.

What changed

  • fzftinty-fzf-theme.sh extracts the generated --color flags into ~/.config/fzf/tinted.sh with a replace-not-append export, so FZF_DEFAULT_OPTS no longer grows on every scheme switch. .zshrc sources the file when present.
  • pitinty-pi-theme.sh maps the palette to pi's semantic tokens and writes ~/.pi/agent/themes/tinted.json, which pi hot-reloads.
  • tuicrtinty-tuicr-theme.sh maps the palette to tuicr's UI keys and emits a tinted.toml plus a base16 .tmTheme for syntax highlighting, blending diff and syntax backgrounds from the panel color.
  • tinty config — registers the three items in config.toml and switches hook execution from zsh -c to the default shell for faster runs.

Compound Engineering
Pi

Add tinted-fzf repo to tinty config.toml with a hook script that
generates a clean ~/.config/fzf/tinted.sh from the current scheme.
Source the generated file from .zshrc so fzf colors match the
active base16/base24 theme.

The hook writes FZF_DEFAULT_OPTS with a clean --color= flag (no
appending) so switching schemes mid-session doesn't bloat the env var.
Generate ~/.pi/agent/themes/tinted.json and ~/.config/tuicr/themes/tinted.toml from tinty's current scheme, alongside the existing fzf hook.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant