-
Notifications
You must be signed in to change notification settings - Fork 36
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
Not compatible with vim-fugitive & git-messenger #30
Comments
I don't use fugitive at the moment. I may try to check it out if I find some time |
I tried vim 8.2 with blamer,fugitive,git-messenger but I could not reproduce the problem. Is this issue still valid ? |
I still have a problem when using |
I created this minimal config for vim 8.2 in my test, which doesn't produce any errors.
Can you try with the same config and let me know if it still produces errors ? |
I tested it with your minimal config and the error still occurs, but not always. "normal" commit messages are not a problem, but if i was in a merge conflict, resolved all conflict and want to commit, the error occurs. E315: ml_get: invalid lnum: 35 I think something get messed up with the removed line numbers. The current document has only 34 lines, after resolving all conflicts. With the conflict markers '<<<<<' and '>>>>>>' 46 lines exists. Hope it helps |
I'm using tpope/vim-fugitive & rhysd/git-messenger.vim, when I add
blamer.nvim
and type the commands like:GitMessage
or:Git log
, the vim(8.2) throw out an error:E315: ml_get: invalid lnum
.The text was updated successfully, but these errors were encountered: