Documentation for hooking into passive behaviors is outdated about vim-eunuch HOT 4 CLOSED

Not even out of date, it's just wrong.

Most people shouldn't need to call EunuchNewLine() at all as Eunuch is pretty good at combining with other maps. I'll update the documentation to reflect that.

from vim-eunuch.

Yeah, in case you just want context for why it's necessary for me . . . I just started using coc for completion and I like to use enter for selecting an entry, but I couldn't get that to work unless I defined it in an after function, and that made both endwise and eunuch functionality not work, so I had to call them manually.

from vim-eunuch.

That coc#pum#visible() ternary that everyone copies and pastes into their vimrc? Should work fine.

from vim-eunuch.

Oh yeah, I'm realizing it's . . . complicated. Long story short, I also use ultisnips so I wrote tab and shift tab in functions because they were getting complicated, so then I also just wrote the enter one in a function even though that's not necessary since enter isn't used by ultisnips. The ternary with <expr> probably does work fine.

from vim-eunuch.