Skip to content
otheme

git-delta

The git-delta target writes ~/.config/git/otheme-delta.conf with palette-derived diff colors and ensures ~/.gitconfig includes it.

This page is generated from the adapter plan used by otheme set vesper --dry-run. Paths are shown exactly as otheme prints them; ~ means your home directory.

Compatibility

Author mode. otheme writes a dedicated git include file with a [delta] section, deriving diff colors from the shared palette, setting the features field to a named delta theme, and pointing syntax-theme at the otheme-derived bat theme.

Files

OrderFileWhat otheme writes
1~/.config/git/otheme-delta.confwrite [delta] config with features=gruvmax-fang, syntax-theme=otheme-vesper, and palette-derived diff colors
2~/.gitconfigadd [include] path = ~/.config/git/otheme-delta.conf if not already present

Enable bat alongside git-delta

git-delta has no syntax engine of its own — it delegates syntax highlighting to bat. The generated [delta] config sets syntax-theme = otheme-<theme-id>, which is the bat theme the bat target authors from the same palette.

For diff token colors to match your theme, enable both targets:

{
  "targets": {
    "git-delta": true,
    "bat": true
  }
}

If git-delta is enabled but bat is not, the referenced otheme-<theme-id> syntax theme won't exist and delta falls back to its default highlighting (diff chrome colors still match, but the code tokens inside diffs won't).

Commands

OrderCommandWhy it runs
1git config --global --listcheck whether the otheme delta include is already present in ~/.gitconfig