Closed Markuzcha closed 2 months ago
Gitsigns has its own set of highlights defined in the docs. It will default to some fallbacks but for the best experience these need to be defined.
Thank you for the quick reply. I found the missing settings for me:
GitSignsAdd = {fg = '#0cbb0c', bg = '#0a0e14'},
GitSignsChange = {fg = '#2085e9', bg = '#0a0e14'},
GitSignsDelete = {fg = '#e00000', bg = '#0a0e14'},
Yet I could omit the setting 'bg' here, as this is already set by SignColum highlight group.
Thank you very much for developing this very useful plugin working in the background, but much more needed than obvious.
Description
It looks like suddenly my color setting for 'DiffChange' is now used for the coloring of changed lines indicator in SignColumn. The other color settings 'DiffAdd' or 'DiffDelete' don't seem to affect Gitsigns line change indicators in SignColumn.
Neovim version
v0.9.5 (LuaJIT 2.1.1702233742)
Operating system and version
Linux
Expected behavior
'DiffChange' not to affect the line change indicator, because I want to keep it this way for my diff views.
Actual behavior
'DiffChange' affects the line change indicator in SignColumn.
Minimal config
Steps to reproduce
mkdir gitsigns_issue
cd gitsigns_issue
git init
touch file
git add file
git commit -m 'initial commit'
nvim --clean -u minimal.lua file
Gitsigns debug messages
No response
Gitsigns cache
No response