-
Notifications
You must be signed in to change notification settings - Fork 297
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
omni complete exits abnormal under NeoVim #310
Comments
Hmm, #305 also relates to completion. I wonder if they are related. |
I just figured it out, neovim would trigger It should be a bug of neovim, BufEnter event should not be triggered when using complete with preview window. |
This is neovim bug? If so, you should create new issue in neovim. |
I think it is not neovim/Vim bug. It is feature. |
@Shougo you're right, both vim and neovim triggered the BufEnter event, but neovim can't works with function |
If I edit some file under git, and use omnifunc to open a completion list, NeoVim will automatically use the first item and exit the completion if and only if the item has an info attribute which will let vim open an preview window to display.
I think this commit 18b7836 is the bad boy.
By the way, this problem will disappear if I add
let g:gitgutter_eager = 0
to my vim config.How to reappear?
Edit any file under git, use ctrl_x ctrl_o to complete, and you will only get the word1.
The text was updated successfully, but these errors were encountered: