feat(gitsigns): support GitSignsCurrentLineBlame highlights #567
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I found that the fg color of
GitSignsCurrentLineBlame
andComment
are the same, which sometimes confuses me:The Comment fg color is
overlay0
now:nvim/lua/catppuccin/groups/syntax.lua
Line 5 in dae42a0
GitSignsCurrentLineBlame
is mapped toNonText
:https://github.com/lewis6991/gitsigns.nvim/blob/749267aaa863c30d721c9913699c5d94e0c07dd3/lua/gitsigns/highlight.lua#L174
And,
NonText
fg color is same withComment
:nvim/lua/catppuccin/groups/editor.lua
Line 30 in dae42a0
What problem does this PR solve?
This PR distinguishes the two, making the
GitSignsCurrentLineBlame
dimmer and making it easier to distinguish between the two.Actual effect
Latte
Frappe
Macchiato
Mocha