You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a bad interaction with deoplete that breaks the mapping.
When I type: fn<CR>, I expect the endwise rule to complete. However, this happens only if deoplete is not enabled. Commenting out the bottom line of the example config disables deoplete and fixes the issue.
This seems to happen because vim.fn.pumvisible() == 1 when the mapping is triggered, even though the popup menu is not displayed. If I disable the check and allow autopairs_cr() to be called directly (instead of esc("<cr>"), the mapping works.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Description
There seems to be a bad interaction with deoplete that breaks the mapping.
When I type:
fn<CR>
, I expect the endwise rule to complete. However, this happens only if deoplete is not enabled. Commenting out the bottom line of the example config disables deoplete and fixes the issue.This seems to happen because
vim.fn.pumvisible() == 1
when the mapping is triggered, even though the popup menu is not displayed. If I disable the check and allowautopairs_cr()
to be called directly (instead ofesc("<cr>"
), the mapping works.Is there some simple way to work around this?
Mapping bug
No response
Steps to reproduce
No response
Minimal config
The text was updated successfully, but these errors were encountered: