-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Column signs not showing when using fugitive's :0Gclog inside git worktree #686
Labels
Comments
Thanks for providing a full issue report (a lot of people don't). I haven't got much experience with bare repos and don't use them, and also being spread quite thin over a few projects, so I'm not likely to look at this for a while. If you want to tackle this yourself (or anyone) then I'm happy to provide help and advice. |
lewis6991
pushed a commit
that referenced
this issue
Dec 15, 2022
lewis6991
pushed a commit
that referenced
this issue
Dec 15, 2022
lewis6991
pushed a commit
that referenced
this issue
Jan 11, 2023
lewis6991
pushed a commit
that referenced
this issue
Jan 11, 2023
lewis6991
pushed a commit
that referenced
this issue
Jan 11, 2023
This was referenced Apr 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Recently noticed this after starting to use git worktrees. Jumping through the quickfix list populated with the file commits by fugitive's
:0Gclog
command does not show the changed hunks in the column bar. However this works fine with a normal non-bare repository.Neovim version
0.8.1
Operating system and version
Ubuntu 20.04 LTS
Expected behavior
No response
Actual behavior
Gitsigns does not return any error. However the hunks of the commits are not displayed nor is it possible to jump between them.
Minimal config
Steps to reproduce
repo setup
nvim --clean -u minimal.lua
foo:0Gclog
commandresult inside bare repo worktree:
![shot_2022-12-14](https://user-images.githubusercontent.com/700372/207608324-84511631-da03-4c00-8dec-9d5a7157223a.png)
result in the normal foo repo:
![shot_2022-12-14](https://user-images.githubusercontent.com/700372/207608731-ce43913c-5f07-44d4-b393-0e1f02042673.png)
Gitsigns debug messages
debug messages on non-bare repo:
debug messages in bare repo:
The text was updated successfully, but these errors were encountered: