Open moetayuko opened 1 year ago
I encountered the same issue 🥲 Any update about this?
Dear maintainers @chemzqm @fannheyward, I discovered that vim-matchup has these two commands:
:NoMatchParen Disable matching after the plugin was loaded.
:DoMatchParen Enable matching again.
The issue can be fixed by using :NoMatchParen
before auto-completion, and using :DoMatchParen
after auto-completion.
However, I was unable to find a suitable autocmd to call these commands automatically.
Could you consider adding autocmds like CocPumCanceled
, CocCompletionDone
? This way, users could manually call :NoMatchParen
to temporarily disable vim-matchup or other conflicting plugins when invoking coc#refresh()
, and let these autocmds actively call :DoMatchParen
to restore the operation of vim-matchup.
@JS-Zheng there's CompleteStop
autocmd, does it work for your case?
@JS-Zheng there's
CompleteStop
autocmd, does it work for your case?
I only discovered the following coc autocmds in Vim:
CocLocationsChange, CocNvimInit, CocStatusChange, CocDiagnosticChange,
CocJumpPlaceholder, CocOpenFloat, CocOpenFloatPrompt & CocTerminalOpen
I believe CompleteStop
is a RPC event, not an autocmd, correct?
https://github.com/andymass/vim-matchup is a popular vim plugin. However, the cursor doesn't behave as expected after expanding some snippets.
MWE
To reproduce
beg<ctrl_l>
The snippet expands correctly, but the cursor doesn't locate at the expected position.
Expected (w/o vim-matchup)
|
denotes cursor positionCurrent (w/ vim-matchup)
It's worth noting that https://github.com/SirVer/ultisnips works correctly with vim-matchup