Tootfinder

Well, to be honest, the default #vim diff colors didn't ever work well for me. Often I'd end up disabling file syntax highlighting because the text colors will become hard to read on top of the bright diff colors.
Today I was working with syncing a bash script with a Windows batch file, so expecting a lot of diff. On top of that, syntax highlighting would be really helpful. So I finally bit the bullet, figured out how to change the colors and then spend half an hour trying to figure out some colors that would actually work for me.
This is what I came up with:
hi DiffAdd ctermbg=17
hi DiffDelete ctermbg=NONE ctermfg=172
hi DiffChange ctermbg=NONE
hi DiffText ctermbg=88
That's:
• dark blue background for added lines with orange fillers in the other buffer
• black/transparent background for changed lines with dark red background for actual changes
I still feel like it's not exactly it. I'm open to suggestions.

Sigh at ensloppification of random software you use. Soon you discover that #Vim maintainers consider it a good idea to use black text on blue background now. In dark theme.

God, what a fucking asshole.
Anyways, I've already spent some time removing #neovim from about half of my build/development containers. For now I'm going back to #vim, but once vim-classic or #evi