git diff added/removed lines colors customization

[scodougy]

Is there a way to change the colors showing the lines added/removed in the diff view? The red and green are not good choices for us with red-green color deficiency (8% of males)

[stefanhaller]

I recommend using a custom pager (I'm a big fan of delta myself). Most pagers allow you to customize the colors; delta does.

Unfortunately you can't use a pager in the staging view yet; this is being worked on, but won't be done any time soon.

[scodougy]

Before I start learning about a custom pager, are you saying it currently wouldn't work anyway in the view I showed in my OP? You 'recommend' a custom pager, but is there any other way to control what colors are used in that view?

[stefanhaller]

are you saying it currently wouldn't work anyway in the view I showed in my OP?

It looks like that screenshot shows the normal diff view; yes, custom pagers work there, that's their main point. The case where they don't is the staging view, i.e. if you press enter on a file to stage individual lines.

I recommend custom pagers not only for customizability of the colors, but for several other reasons. The two main ones for me are highlighting of changed words within a line, and delta's feature of making line numbers clickable (you can click on them and this takes you directly to the editor on that line; huge time saver).

(Another limitation of custom pagers is that they currently don't work on Windows, though.)

is there any other way to control what colors are used in that view?

Yes, and I guess I should have answered this first. Without a pager, it is git that produces those colors, not lazygit. You can customize them by putting something like this in your ~/.gitconfig file:

[color "diff"]
	new = "#22aaff"
	old = "#ffaa33"

[scodougy]

Thanks, that's just what I needed for the short run, as well as something to look into for the long run. I saw other color settings in lazygit's config and presumed that was 'the way', but now I see more of what you're doing.

FWIW, I'm very happy with the tool so far. I have bound it to a keystroke within vim and it integrates very well as a shelled-out subprocess (:!lazygit). When I get around to learning Go, maybe I can help contribute. :-)