Closed thepenguinthatwants closed 4 years ago
Thank you for the report and I successfully reproduced the problem.
Well... I don't know the detail of implementation of animate.vim and lens.vim. But this is my theory.
If this theory is correct, I believe this is an issue of animate.vim or lens.vim, not vim-mundo. How do you think?
Yeah you are right! Its certainly not a problem of this plugin. Mundo has always being very nice plugin.
Its just that I was suprised for it to affect mundo.
@thepenguinthatwants Well this is just a theory, and there is a chance that Mundo actually has a problem. 😅 I don't know how to do it yet but maybe vim-mundo can workaround this problem without changing animate.vim or lens.vim
Please let me know if it there is an actual issue of vim-mundo, or if you find out how to workaround this problem. Thanks!
you can disable lens.vim
for specific filetypes, namely Mundo
and MundoDiff
, with the
g:lens#disabled_filetypes
options. i.e.
let g:lens#disabled_filetypes = ['Mundo', 'MundoDiff']
you can determine a buffer's filetype with the command :set ft?
.
it seems there was a problem with lens.vim
and animate.vim
after all and setting this option does not functin as expected unless animate.vim
is disabled. see issue #12 from lens.vim
. you can resolve the issue by plugging a fork by ipod825, who has also implemented a seperate resizing plugin based on user defined rules. you might also apply the diff manually as it just a few lines.
Hi! For some reasons with these plugins
mundo cant choose other objects and it just when pressing j it randomly jumps into other buffers.