You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After using Gitsigns show ... to open specific snapshot of a file, Gitsigns blame_line doesn't work correctly on that snapshot. It often just pops up Not Committed Yet window, instead of actually blaming the line.
Neovim version
NVIM v0.10.0
Operating system and version
Arch Linux (x86_64) Kernel: 6.9.2-arch1-1
Expected behavior
Gitsigns blame_line actually blames lines in older file snapshots.
Actual behavior
For some lines (both changed and unchanged by current snapshot), it just shows Not Committed Yet window, instead of actual commit.
Strangely enough, despite the error, everything works as expected in all later steps.
Would you prefer that I close this issue (since it's now solved) and open another one for this error or should I just wait and close this once the show error is fixed?
Description
After using
Gitsigns show ...
to open specific snapshot of a file,Gitsigns blame_line
doesn't work correctly on that snapshot. It often just pops upNot Committed Yet
window, instead of actually blaming the line.Neovim version
NVIM v0.10.0
Operating system and version
Arch Linux (x86_64) Kernel: 6.9.2-arch1-1
Expected behavior
Gitsigns blame_line
actually blames lines in older file snapshots.Actual behavior
For some lines (both changed and unchanged by current snapshot), it just shows
Not Committed Yet
window, instead of actual commit.Minimal config
Steps to reproduce
modify first two lines
)aaaa
) in order to see who introduced it.modify first two lines
introduced it.bbbb
) which was introduced by the samemodify first two lines
commit.bbbb
) in order to see who introduced it.Not Committed Yet
popup, instead ofmodify first two lines
.ccc
) which wasn't modified by this commit.Not Committed Yet
popup, instead of initial commitadd 3 lines
.Gitsigns debug messages
No response
The text was updated successfully, but these errors were encountered: