Closed calebeby closed 2 years ago
Can confirm, with a minimal vimrc
set nocompatible
call plug#begin('~/.vim/bundle')
Plug 'https://github.com/tpope/vim-sensible'
Plug 'https://github.com/simnalamburt/vim-mundo'
call plug#end()
You don't need to even write or close the file to trigger the error.
git bisect
shows that it was broken by c0d814b9c1acb6031d6669b0b7118b8f07c39def from #122.
The workaround is just manually checkout the previous working commit in the plugin directory (assuming a plugin manager): 595ee332719f397c2441d85f79608113957cc78f
Since every :PlugUpdate
breaks this again, a slightly more permanent fix is to use my fork which I will keep at 595ee33 until this issue is fixed:
Plug 'TamaMcGlinn/vim-mundo'
I will delete my fork when this issue is fixed, so you get an error and will know to switch back.
Thank you @simnalamburt, works great!
Here are the steps I did:
nvim ~/.vimrc
Then this error pops up:
I repeatedly press
<esc>
to close the error message and it keeps popping up, exactly the same, with the same undo number in the message.If I switch to the editor view and make edits to the file, the undo tree is refreshed and I can go back to the undo tree without errors. It shows all the previous history correctly.
Python information in
:checkhealth
:Let me know if there's any more information that would help diagnose the issue!