Open TangMonk opened 7 years ago
What is your environment? It seems Vim/neovim bug instead of the plugin.
I am using neovim 0.2, OS X 10.11, Iterm2
I believe this is neovim issue, too. I don't have this issue, though.
Try using a release version of neovim, in case you're using the master version.
A release version should be considered more stable.
The master version is not as stable, from my experience, for example https://github.com/roxma/nvim-completion-manager/issues/6#issuecomment-277434983.
@roxma I am install from homebrew, it might the stable version, I am not build from the source code
It seems you could choose stable or head version with homebrew, you should verify your installation.
@roxma
$ brew info neovim
neovim: stable 0.2.0 (bottled), HEAD
Ambitious Vim-fork focused on extensibility and agility
@TangMonk I got the same issue. It's definitely issue of neovim. It happens sporadically and I can't reproduce it on purpose
I have seen that once in a while also
➜ ~ brew info neovim
neovim: stable 0.2.0 (bottled), HEAD
Ambitious Vim-fork focused on extensibility and agility
https://neovim.io/
/usr/local/Cellar/neovim/0.2.0_1 (1,352 files, 17.2MB) *
Poured from bottle on 2017-07-12 at 14:53:37
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/neovim.rb
==> Dependencies
Build: luajit ✘, cmake ✔, lua@5.1 ✘, pkg-config ✔
Required: gettext ✔, jemalloc ✔, libtermkey ✔, libuv ✔, libvterm ✔, msgpack ✔, unibilium ✔
Please check the gif animation:
this weird problem will occur some times and not very often, I am not sure how to reproduce it.
I have to close the vim instance and reopen vim to fix that problem