lifepillar / vim-mucomplete

Chained completion that works the way you want!
MIT License
913 stars 18 forks source link

CPU issue with ultisnips #57

Closed LambdaHJ closed 7 years ago

LambdaHJ commented 7 years ago

I've been using this plugin for some time, it is very nice. but I can not make mucomplete work with ultisnips.CPU is high load, vim no response. error

vim --version VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Mar 17 2017 00:01:12) MacOS X (unix) version Included patches: 1-473

settings:

set noshowmode shortmess+=c
set noinfercase
set completeopt-=preview
set completeopt+=longest,menuone,noinsert,noselect

let g:mucomplete#chains = {
        \ 'default' : ['file', 'omni', 'keyn', 'dict'],
        \ 'vim'     : ['file', 'cmd', 'keyn'],
        \ 'python'  : ['file', 'omni', 'ulti'],
        \ 'cpp'     : ['file', 'ulti', 'keyn', 'incl', 'omni', 'dict']
        \ }

let g:mucomplete#enable_auto_at_startup = 1

imap <Leader>j <plug>(MUcompleteCycFwd)
imap <Leader>k <plug>(MUcompleteCycBwd)

How can I solve this problem?

lifepillar commented 7 years ago

I cannot reproduce it. Please follow the steps described at :help mucomplete-troubleshooting. In particular, does that happen when you invoke UltiSnips expansion directly? Can you reproduce the problem using the minimal vimrc provided with µcomplete? Which version of µcomplete are you using?

LambdaHJ commented 7 years ago

I am sorry. jedi cause this problem. very nice plugin