Skip to content
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

:Git command fails with an error Can't open file syntax/diff.vim #2346

Closed
olzhasar opened this issue Oct 7, 2024 · 4 comments
Closed

:Git command fails with an error Can't open file syntax/diff.vim #2346

olzhasar opened this issue Oct 7, 2024 · 4 comments

Comments

@olzhasar
Copy link

olzhasar commented Oct 7, 2024

I recently started experiencing a weird error when trying to run the :Git command:

Error detected while processing BufReadCmd Autocommands for "fugitive://*"..function fugitive#BufReadCmd[8]..fugitive#BufReadStatus[28]..BufReadCmd Autocommands for "fugitive://*"..function fu
gitive#BufReadCmd[8]..fugitive#BufReadStatus[23]..FileType Autocommands for "*"..Syntax Autocommands for "*"..function <SNR>12_SynSet[26]..script /Users/***/.local/share/nvim/site/pack/pack
er/start/vim-fugitive/syntax/fugitive.vim:                                                                                                                                                      
line    8:                                                                                                                                                                                      
E484: Can't open file syntax/diff.vim 

Will appreciate any help with that issue.

Neovim v0.10.2
Fugitive @d4877e54cef67f5af4f950935b1ade19ed6b7370
MacOS

@davidwding
Copy link

I'm running into this exact same issue.

@tpope
Copy link
Owner

tpope commented Nov 12, 2024

Does $VIMRUNTIME/syntax/diff.vim actually exist?

@davidwding
Copy link

Yes, it does exist. For what it's worth, I use vim-plug and ran :PlugUpdate, which seems to have resolved the issue.

@olzhasar
Copy link
Author

My case might also have been resolved by an update, haven't seen this in a while.
Will close the issue for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants