haorenW1025

Ahh also @Shougo Thanks a lot for help testing it:) Really appreciate!

@tami5 After some investigation, I think I know why the flickering happens. This is because when supporting fuzzy completion we'll have to manually triggered complete instead of let neovim filter...

Thanks for the kind words:) > The issue seems to be that complete_item is a nil value, and when you access complete_item.user_data, it issues an exception. Hmm normally `complete_item` will...

I'm very sorry for the long wait. I've been too busy to do anything last couple of weeks or so. I'll start looking into it.

Okay so first of all what you're showing in your gif is signature help. If you want to disable that you should use `g:completion_enable_auto_signature = 1`, the weird behavior in...

auto_popup is only for popup of completion! Also thanks for the extra information, I can’t figure what went wrong this afternoon so you help me big time!

Hmm the issue still exist `let loaded_matchparen = 0` and I'm kind of lost because it works fine on my full config, I copied almost every config about completion-nvim in...

Hmm a problem is right now I'm using location list as a driver for the `:NextDiagnostic`, `:PrevDiagnostic` stuff, and disable location list will break those things. So this should be...

Yeah, if we want both neomake's linting and lsp diagnostic work at the same time without any conflict, one way is not using location list at all and implement our...

> As far as I understand, your implementation for jumping to the next one is similar to :lnext but the navigation starts from the current line. Is that correct? Yes,...