Renderers like delta and difftastic pick their colors for either a dark
or a light background, and they can't find out which one the terminal
has. Lazygit runs them with TERM=dumb, in a pty that doesn't answer
their queries. So the colors come from the config, and when the
terminal switches between dark and light, the diff keeps the ones it
has.
Add {{colorScheme}} to the commands of diff renderers. It is 'dark' or
'light', going by gui.colorScheme, or by the terminal if that is
'auto'. It can be passed to delta as --{{colorScheme}} and to
difftastic as --background={{colorScheme}}; other renderers can choose
between options with a template expression. When the terminal switches
between dark and light, render the diff again.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
5.1 KiB
Custom Diff Renderers
Custom diff renderers are useful for showing a better rendering of a diff than git's builtin raw diff, and using one is strongly recommended (I personally prefer delta myself, but that's a matter of personal preference). There are three types of diff renderers that lazygit supports:
- stdin filters, e.g. delta and diff-so-fancy. They take git's raw output as stdin and produce something nicer on stdout, and they are hooked up using git's GIT_PAGER mechanism. (These used to be called "custom pagers" in earlier lazygit versions.)
- external diff programs, e.g. difftastic; these are called using git's
--ext-diffflag, and they take over diff generation from git completely rather than post-processing git's output. - git's raw output using custom arguments; mainly useful for
--color-words(or--word-diffif you are color blind).
Diff renderers are configured with the diffRenderers array in the git section of lazygit's config file; it is an array because you can have multiple entries that you can cycle through with the | key. This can be useful if you usually prefer a particular diff renderer, but want to use a different one for certain kinds of diffs.
Fields that are shared by all renderer types:
- type The type of diff renderer; choices are
stdinFilter,extDiff, orrawGit.stdinFilteris the default, because it's the most common one; so you can omit this if you use delta. - name A name that is shown in the status bar toast when cycling renderers; defaults to the first word of the renderer command, but can be useful e.g. to distinguish "delta" from "delta side-by-side" if you have entries for both.
Fields only for stdinFilter:
-
command The command line to use for
GIT_PAGER. -
colorArg whether you want the
--color=alwaysarg in yourgit diffcommand. Some diff renderers want it set toalways, others want it set tonever. The default isalways, since that's what most renderers need.
Fields only for extDiff:
- command The command line to use for the
diff.externalgit config. If left empty, it uses the global value of git'sdiff.externalconfig; this can be useful if you also want to use it for diffs on the command line, and it also has the advantage that you can configure it per file type in.gitattributes; see https://git-scm.com/docs/gitattributes#_defining_an_external_diff_driver.
Fields only for rawGit:
- args The additional arguments to use in the
git difforgit showcall (e.g.--color-words), as an array of strings.
The command of a stdinFilter or extDiff renderer is a Go template with these variables:
{{width}}: the width of the view that the diff is rendered into.{{colorScheme}}:darkorlight, depending on whether the terminal has a dark or a light background. Lazygit asks the terminal about this; if yours doesn't tell, setgui.colorScheme.{{columnWidth}}(only forstdinFilter): the width of one side of a side-by-side rendering, e.g. forydiff -p cat -s -w {{columnWidth}}.{{diffContext}}(only forextDiff): lazygit's current diff context size, the value controlled by the{/}keybindings.
A variable can also be written with a leading dot, as in {{.width}}. The command can use template expressions too; for example, delta --paging=never {{if gt .width 160}}--side-by-side{{end}} shows the diff side by side only when there is room for it, or delta --syntax-theme={{if eq .colorScheme "light"}}Github{{else}}Dracula{{end}} picks a different syntax theme based on the background.
Here's an example for a multi-renderer setup:
git:
diffRenderers:
- command: delta --{{colorScheme}} --paging=never
- command: ydiff -p cat
colorArg: never
- type: extDiff
command: difft --color=always --background={{colorScheme}} --context={{diffContext}}
- type: rawGit
args: [--color-words]
name: color-words
- type: rawGit # git's default diff
name: default
Delta:
git:
diffRenderers:
- command: delta --{{colorScheme}} --paging=never
--{{colorScheme}} passes --dark or --light to delta, so that it matches the background of your terminal.
A cool feature of delta is --hyperlinks, which renders clickable links for the line numbers in the left margin, and lazygit supports these. To use them, set the command: field to delta --{{colorScheme}} --paging=never --line-numbers --hyperlinks --hyperlinks-file-link-format="lazygit-edit://{path}:{line}"; this allows you to click on an underlined line number in the diff to jump right to that same line in your editor.
Note that delta's --navigate option doesn't work in lazygit, for technical reasons.
Diff-so-fancy
git:
diffRenderers:
- command: diff-so-fancy
ydiff
gui:
sidePanelWidth: 0.2 # gives you more space to show things side-by-side
git:
diffRenderers:
- colorArg: never
command: ydiff -p cat


