Andy Massimino

Thanks. I'm not sure yet where the problem is but that helps, I'll have to test shortly. The other thing to try is deferred matching, which uses different code paths....

Great, thanks! That provides two viable workarounds, however I'd like to keep this issue open so I get a chance to investigate where the problem is to possibly contribute back...

That's unfortunate. Do you mean when you type literal `foo(` in vim+coc.nvim+ccls specifically with deferred matching, no signature popups up? Is the occurrence of the `(` is important here? The...

There is also the option `g:matchup_matchparen_pumvisible = 0` but whether it would work in these cases likely depends on the plugin's order of operations. Do you offhand know if there's...

Thanks, ok so I'd I understand correctly I would have to listen to that autocmd and if it's triggered disable matching temporarily? "Temporary one shot disable" is a generic enough...

Unless there is an autocmd for when a snippet is expanded.

Oddly, I don't see CocOpenFloat getting triggered at all (coc.nvim version: 0.0.74).

Wait so is CocOpenFloat neovim only? I can't figure out any way to detect when a popup window is currently open in vim. I'd prefer not to use 'g:matchup_matchparen_nomode' if...

There are two issues in this issue. I think I fixed the _second_ one under mysterious circumstances. So `g:matchup_matchparen_deferred=1` should work in both cases.

Like in the SQL case, I cannot think of a way to handle this correctly with the current implementation using `b:match_words` regular expressions. The reason is there needs to be...