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

Not compatible with vim-fugitive & git-messenger #30

Open
weiguoz opened this issue Sep 29, 2020 · 5 comments
Open

Not compatible with vim-fugitive & git-messenger #30

weiguoz opened this issue Sep 29, 2020 · 5 comments
Labels
bug Something isn't working

Comments

@weiguoz
Copy link

weiguoz commented Sep 29, 2020

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.

@APZelos
Copy link
Owner

APZelos commented Nov 9, 2020

I don't use fugitive at the moment. I may try to check it out if I find some time

@georgesofianosgr georgesofianosgr added the bug Something isn't working label Mar 19, 2021
@georgesofianosgr georgesofianosgr changed the title Compatibility with other plugins Not compatible with vim-fugitive & git-messenger Mar 19, 2021
@georgesofianosgr
Copy link
Collaborator

georgesofianosgr commented Mar 20, 2021

I tried vim 8.2 with blamer,fugitive,git-messenger but I could not reproduce the problem. Is this issue still valid ?

@reybeamde
Copy link

I still have a problem when using :Gstatus. If i use cc to enter a commit message or g? to show help, the error still occurs. (vim 8.2)

@georgesofianosgr
Copy link
Collaborator

I created this minimal config for vim 8.2 in my test, which doesn't produce any errors.

set nocp

call plug#begin('~/.local/share/vim/plugged')
Plug 'APZelos/blamer.nvim'
Plug 'tpope/vim-fugitive' 
Plug 'rhysd/git-messenger.vim'
call plug#end()

let g:blamer_enabled = 1
let g:blamer_delay = 500
let g:blamer_relative_time = 1
let g:blamer_show_in_visual_modes = 1
let g:blamer_show_in_insert_modes = 0

Can you try with the same config and let me know if it still produces errors ?
Also does :GitMessage & :Git log produces the same error as OP ?

weiguoz added a commit to weiguoz/zdots that referenced this issue Mar 24, 2021
@reybeamde
Copy link

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
E315: ml_get: invalid lnum: 36
....
E315: ml_get: invalid lnum: 45

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants