Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

neovim and deoplete-jedi doesn't work well with forked snipmate #191

Open
fission1110 opened this issue Aug 31, 2017 · 0 comments
Open

neovim and deoplete-jedi doesn't work well with forked snipmate #191

fission1110 opened this issue Aug 31, 2017 · 0 comments

Comments

@fission1110
Copy link

Thank you for this plugin.
Years ago I gave up with making vim's tab behave more "ide like" and do completion with snippets.
Today I decided to give it another go and your plugin does exactly what I want.

I'm using deoplete's "complete as you type asynchronously" behavior with deoplete-jedi for python omni completion.
Well.. deoplete-jedi contains all language keywords for python, so it shows the popup menu for all of my snippets.

This breaks your snipmate fork, because if pumvisible() is true, it ignores the snippets and tries to do the default supertab behavior.
I would really like it to attempt the snippet before doing the completion behavior at all costs.

It would be nice if this were configurable.

https://github.com/ervandew/snipmate.vim/blob/7d57812381607a735ac25a6192ad17d63f1e4c7f/plugin/snipMate.vim#L168

if pumvisible() " Update snippet if completion is used, or deal with supertab
    if exists('SuperTabKey')
        call feedkeys(SuperTabKey) | return ''
    endif
    call feedkeys("\<esc>a", 'n') " Close completion menu
    call feedkeys("\<tab>") | return ''
endif
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant