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

codi.vim doesn't work well with ultisnips #68

Open
ashfinal opened this issue May 31, 2017 · 2 comments
Open

codi.vim doesn't work well with ultisnips #68

ashfinal opened this issue May 31, 2017 · 2 comments

Comments

@ashfinal
Copy link

ashfinal commented May 31, 2017

I've installed ultisnips plugin, and it worked well without codi.vim.

But while using codi.vim, ultisnips' jumpforward and backward do not work totally.

I have these config in my .vimrc file:

let g:UltiSnipsExpandTrigger = "<Tab>"
let g:UltiSnipsJumpForwardTrigger = "<Tab>"
let g:UltiSnipsJumpBackwardTrigger = "<S-Tab>"

I'm wondering if there is a way that the two plugins co-work well?

@metakirby5
Copy link
Owner

Codi generally does not play well with stateful plugins like Ultisnips because a lot of buffer switching is involved in updating the results pane. #3 may be related.

@ashfinal
Copy link
Author

ashfinal commented Jun 1, 2017

But since ultisnips is such a generally installed plugin, I guess solving this problem will benefit lots of people. :)
As for conflict problem, vim-multiple-cursors seems have the same issue. But the workaround that they provide works well on me: interactions-with-other-plugins. Hope this may help solving this problem, or not ;(

Still, thanks for your wonderful plugin. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants