AutoPairsMapCR conflicts with neocomplete

[marlun]

You can take a look here Shougo/neocomplete.vim#281 for a problem summary. The AutoPairsMapCR conflicts with neocomplete in a way shown here https://cloudup.com/coUNwukTSRj

In the following code X stands for the cursor. My starting point is the following code:

Plugin 'sjl/gundo.vim'
X

I want to be able to write

Plugin 'sjl/gundo.vim'
Plugin 'ShoX'

get the neocomplete popup window, hit ENTER to select the chosen item and get

Plugin 'sjl/gundo.vim'
Plugin 'ShougoX'

but still be able to use auto-pairs functionality to change

... {X}

into the following

... {
  X
}

You can read more about it on the neocomplete issue Shougo/neocomplete.vim#281

I can write more about the problem here if you're not OK with reading the neocomplete issue.

Also, I'm aware of #16 but it does not seem to help me.

[ysolis]

I use deoplete (from the same author of neocomplete for vim 7.x but for NeoVim), neosnippets and autopairs. I did have the original problem described in Shougo/neocomplete.vim#281 and yes, this problem did "resolve" with:

let g:AutoPairsMapCR=0

Now, for recover the AutoPairsMapCR functionality, I wrote this in my config (must be modified for vim with neovim but this have the idea):

let g:AutoPairsMapCR=0
imap <expr><CR> pumvisible() ? deoplete#mappings#close_popup() : "\<CR>\<Plug>AutoPairsReturn"

You can use this like base for a config change in vim. The only condition is that AutoPairsReturn only can be used alone in vim 7.4+ or neovim 1.4+, I think that must be more complicated with 7.3/7.2/old versions.