rafaqz
commented
6 years ago I never get that error and I use this plugin constantly in vim (sometimes nvim).
To track this down you should run ranger.vim on a clean vimrc with no other packages or customisation. If it is still an issue please post the version of everything relevant: ranger, vim, nvim and post the text of the error message.
If that fixes the issue, incrementally add your packages/custom code until you find what is breaking it. Then run it with just that thing and make sure it's still causing the error. Then post here outlining the source of the problem.
Then we should be able to fix it. Otherwise I don't know what would cause that, and can't really investigate it in any way.
PGimenez
I kept getting the error "Can only call this function in an unmodified buffer" when using the plugin. Ranger opens fine, but it can't tell vim/nvim to open the file it picks. The annoying thing is that I'm not sure what triggers this. As my session grows longer, it becomes more likely for me to hit this error. I though it was NERDTree messing things up, but even when I uninstalled it, the problem persists.
I don't know what triggers this. Editing, saving, closing windows/tabs, .... I've tried it all. It's just that sometimes the bug happens, and sometimes it doesn't. I'm sorry that this problem is not easy to reproduce so I can't give you the steps to get it. Maybe there is indeed a plugin which is interfering with it. The only thing I know is that whenever the bug happens, I have to restart vim before being to use ranger again. But can we stop checking whether the buffer is modified or not? Or is it something hard-coded into vim/nvim? Using the latest vim/nvim.