-
-
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
Error when opening a file revision with blame enabled #1093
Comments
Works for me Screen.Recording.2024-08-02.at.09.29.54.movIs 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.
My git version is:
Further, looking at git-blame docs:
So I bet you have git v2.41 or greater. |
Hmm I might be able to workaround this. If revision is specified, then most of the time |
This comment was marked as spam.
This comment was marked as spam.
#1177 will avoid the issue most of the time but not completely. |
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
The text was updated successfully, but these errors were encountered: