-
-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some highlights configuration does not correctly fallback #729
Labels
bug
Something isn't working
Comments
The first line uses |
|
Do you have set |
No I don't. |
lewis6991
added a commit
that referenced
this issue
Jan 27, 2023
Ok, I think it's because the fallbacks aren't defined when Gitsigns sets up its highlights. #730 should fix it. Can you check? |
That was fast! Tested #730 here, the issue has been fixed!! 👍 Thank you!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The documentation says that:
GitSignsChangedeleteNr
fallbacks toGitSignsChangeNr
GitSignsTopdeleteNr
fallbacks toGitSignsDeleteNr
GitSignsUntrackedNr
fallbacks toGitSignsAddNr
I do have
GitSignsChangeNr
GitSignsDeleteNr
GitSignsAddNr
setting in place, butGitSignsChangedeleteNr
GitSignsTopdeleteNr
GitSignsUntrackedNr
are not inheriting the configuration, I have to manually set it to work.Without extra configuration the line number is shown as if there were no changes (color does not change).
Neovim version
v0.8.2
Operating system and version
Arch Linux x86_64 6.1.7-arch1-1
Expected behavior
I expect the setting to fallback.
Actual behavior
The setting is not fallback and I have to set manually.
Minimal config
Steps to reproduce
Do the following in a file managed by git and without changes:
nvim --clean -u minimal.lua some_file
:set number
to show line numbersGitSignsDeleteNr
, but it stays the same color (as if unchanged).Do some other changes that triggers
GitSignsChangedeleteNr
orGitSignsUntrackedNr
and see that it does not fallback.Gitsigns debug messages
No response
The text was updated successfully, but these errors were encountered: