Open stv17 opened 1 month ago
Works for me
https://github.com/user-attachments/assets/cf571836-22f5-4ca6-9304-2ac816a9ab82
Is it perhaps your version of git?
Can you run:
cat minimal.lua | git blame --contents - --incremental @ -- minimal.lua
Hello, indeed it'd appear to be the git version.
The command you suggested (cat minimal.lua | git blame --contents - --incremental @ -- minimal.lua
) throws the same error I see in neovim:
fatal: cannot use --contents with final commit object name
My git version is:
git version 2.39.2
Further, looking at git-blame docs:
So I bet you have git v2.41 or greater. Thanks for your feedback, in my case this will be solved by the next git update from Debian.
Hmm I might be able to workaround this. If revision is specified, then most of the time --contents
shouldn't be needed.
Description
First of all, thanks for your work on this plugin. I mostly use it for signs but I appreciate the new features and hope it continues to evolve. This is my first issue report.
When viewing the revision of a file (like with
:Gedit @^:%
from vim-fugitive or:Gitsigns show @^
if you have optioncurrent_line_blame
enabled then an error pops up. I think this started happening not long ago, but I can't say which version of gitsigns I was using at the time.Do note that the option in question is given disabled by the README config.
Neovim version
NVIM v0.10.1-dev-55+g9c6efd0a6
Operating system and version
Debian stable (Bookworm)
Expected behavior
From the README comment on integration with fugitive I take the revision should show the signs relative to it's parent (as I think it always did).
Actual behavior
This error pops up:
The
--contents
flag is probably added by file "lua/gitsigns/git/blame.lua".Minimal config
Steps to reproduce
A simple setup:
And now in neovim do
:Gitsigns show @
Gitsigns debug messages
Gitsigns cache
No response