issue with neocomplete plugin #283

Closed
Netherdrake opened this Issue Sep 22, 2013 · 6 comments

Projects

None yet

6 participants

@Netherdrake

Hi,

I've just started using neocomplete plugin (https://github.com/Shougo/neocomplete.vim), but I get 2 errors on every ruby file when trying to edit them.

^@ completefunc=syntaxcomplete#Complete^@^ILast set from ~/.vim/bundle/neocomplete/autoload/neocomplete/init .vim

and
Another plugin set completefunc! Disabled neocomplete.

This only happens when vim-rails is installed. Do you happen to have any suggestions on how could I fix this issue?

@mikekreeki

+1

@yoneapp
yoneapp commented Sep 26, 2013

+1

@Shougo
Shougo commented Sep 26, 2013

Hi, I'm neocomplete author. It is vim-rails problem. Not neocomplete.

https://github.com/tpope/vim-rails/blob/master/autoload/rails.vim#L4468

vim-rails overwrites completefunc. So neocomplete disabled.
You can overwrite completefunc by g:neocomplete#force_overwrite_completefunc.

@t-cyrill
t-cyrill commented Mar 6, 2014

+1

@tpope
Owner
tpope commented Mar 6, 2014

I'm tentatively dropping 'completefunc' support, because I'm not sure anybody really even cares about it and it's a one liner in your vimrc if you do. But for the record, I don't really think yelling at the user for something like that is a feature.

@tpope tpope closed this Mar 6, 2014
@baocaixiong baocaixiong added a commit to baocaixiong/DotFiles that referenced this issue May 11, 2014
@baocaixiong baocaixiong tpope/vim-rails#283 (comment) 67c4d3b
@CodeFalling CodeFalling referenced this issue in justmao945/vim-clang Aug 23, 2014
Closed

Work with neocomplete #15

@Shougo
Shougo commented Nov 19, 2014

But for the record, I don't really think yelling at the user for something like that is a feature.

@tpope OK. I improved the message.

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