-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
gitblame_enabled=0 not working in lunar vim #65
Comments
Hi! Thanks for your report! My guess is once the |
Hey! Would implementing #69 be good enough for this use case? I want to switch to a |
@f-person I think implementing a |
For me calling Instead running Note: I am using regular NeoVim and not LunarVim. |
I was having the same issue on neovim 0.9. Running the cmd as @moizalicious indicated somewhat worked. I was still getting one git blame on the first line of the first file that I opened. 🤷♂️ I fixed it with init'ing with lazy.nvim when loading the function. Hopefully this will help @yannk and others.
|
There was an [issue](f-person/git-blame.nvim#65) on git-blame.nvim about `vim.g.gitblame_disable = 0` not working with Lunar. I recently implemented a setup function which solves this issue. This commit uses `setup`, instead of legacy vim.g in order to avoid any confusions for users who wanna use git-blame :).
This is fixed now! You should switch to require("gitblame").setup { enabled = false } Also opened a PR for LunarVim docs: LunarVim/lunarvim.org#421 |
There was an [issue](f-person/git-blame.nvim#65) on git-blame.nvim about `vim.g.gitblame_disable = 0` not working with Lunar. I recently implemented a setup function which solves this issue. This commit uses `setup`, instead of legacy vim.g in order to avoid any confusions for users who wanna use git-blame :).
Similar to #55 I see the configuration in lunar vimdocs not working
https://www.lunarvim.org/docs/plugins/extra-plugins#git-blame
versions:
The text was updated successfully, but these errors were encountered: