maralla / completor.vim

Async completion framework made ease.
MIT License
1.29k stars 63 forks source link

Completor freaking out after update #216

Closed tomaskallup closed 5 years ago

tomaskallup commented 5 years ago

Today I updated my vim plugins and completor started freaking out, whenever I start typing and the completor popup triggers, it deletes everything I typed and show the completion popup.

completor-weirdness

My vim: VIM - Vi IMproved 8.1 (2018 May 18, compiled Aug 7 2018 21:58:18) macOS version Included patches: 1-250

Completor: On master -> 3461d62 I'm also using completor-typescript Options:

let g:completor_node_binary = '/usr/local/bin/node'
let g:completor_css_omni_trigger = '([\w-]+|@[\w-]*|[\w-]+:\s*[\w-]*)$'
let g:completor_auto_trigger = 1

Previously this didn't happen and completor worked fine.

After further testings seems like it might be related to 'jedi-vim'

I was able to reproduce this with these plugins:

Plug 'leafgarland/typescript-vim'
Plug 'peitalin/vim-jsx-typescript'
Plug 'maralla/completor.vim', { 'do': 'make js' }
Plug 'maralla/completor-typescript'
Plug 'davidhalter/jedi-vim'

Disabling jedi-vim seems to have fixed it.

hanqing0521 commented 5 years ago

I have the same problem with my two device vim completor. I rest to old version d404cea to let it work. I am waiting for you to fix the bug, Thanks

maralla commented 5 years ago

What is the result of :echo g:completor_complete_options and :echo &cot?

tomaskallup commented 5 years ago

g:completor_complete_options - menuone,noselect,preview &cot - menuone,longest,preview

maralla commented 5 years ago

The commit ab49c6797c85e36f3cc2884ab03d948abb4dd1e8 fixed the problem please update.

tomaskallup commented 5 years ago

Thanks, that seems to work!

codito commented 5 years ago

Looks like this behavior has regressed recently. Able to reproduce on 09ff214. Doesn't repro with 9d1b13e8da0.

maralla commented 5 years ago

The commit cea1fd674e59521fb5ce5f2d10901eac3a5bcb1c fix the problem. @codito

codito commented 5 years ago

It's working great now. Thanks for quick response!