Conflict with AutoComplPop -- E764: Option 'omnifunc' is not set

Question

Conflict with AutoComplPop -- E764: Option 'omnifunc' is not set

markgamis opened this issue 12 years ago · comments

I installed xml.vim with AutoComplPop (http://www.vim.org/scripts/script.php?script_id=1879) annd when i open an xml (or html file), as soon as I type < , I get a "E764: Option 'omnifunc' is not set" error, and vim will keep on complaining with the same error for every character i type until i close it with a >.

After that, the tag is auto-closed as expected.

Devin Weaver · Answer 1 · Mon Aug 13 2012 21:25:55 GMT+0800 (China Standard Time)

A quick google search found this article which quotes:

If you get an error like E764: Option 'omnifunc' is not set, then run :runtime! autoload/pythoncomplete.vim to load the omnicompletion plugin.

Mark Gamis · Answer 2 · Tue Aug 14 2012 23:48:27 GMT+0800 (China Standard Time)

Didn't work. Thanks for the response anyway.

To clarify, the error doesn't happen if the two plugins (AutoComplPop and
xml.vim) are NOT enabled at the same time.

On Mon, Aug 13, 2012 at 9:25 PM, Devin Weaver notifications@github.comwrote:

A quick google search found this articlehttp://www.swaroopch.org/notes/Vim_en:Programmers_Editorwhich quotes:

If you get an error like E764: Option 'omnifunc' is not set, then run :runtime!
autoload/pythoncomplete.vim to load the omnicompletion plugin.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/15#issuecomment-7691584.

Mark Gamis
"It seems that perfection is reached not when there is nothing left to add,
but when there is nothing left to take away"

Marc Alexandre · Answer 3 · Sun Oct 21 2012 22:34:49 GMT+0800 (China Standard Time)

I can confim the issue. I already tried what the article said, but it didn't do anything.

Devin Weaver · Answer 4 · Mon Oct 22 2012 22:31:55 GMT+0800 (China Standard Time)

I don't have any knowledge on AutoCompPop. Does anyone have any experience with that plugin / codebase? I'd like to get some feedback about the plugin and how it works before I start hacking away at a kludgy workaround.

othree · Answer 5 · Wed Feb 06 2013 12:08:18 GMT+0800 (China Standard Time)

autocmd FileType xml set omnifunc=xmlcomplete#CompleteTags noci
autocmd FileType html set omnifunc=htmlcomplete#CompleteTags noci

In your vimrc

Jonah · Answer 6 · Fri Feb 22 2013 08:27:12 GMT+0800 (China Standard Time)

Thanks othree, I had the same problem and that worked

Devin Weaver · Answer 7 · Fri Feb 22 2013 21:34:15 GMT+0800 (China Standard Time)

Added fix to README file.

othree · Answer 8 · Fri Feb 22 2013 21:47:10 GMT+0800 (China Standard Time)

I think this is not a conflict.
This should be autocomplpop's issue.
It will auto trigger omnicomplete for xml.
But people might not set it correctly.
Since the autocomplpop is not update any more for 2 years.
I have forked it and try to improve it.
I will try to solve this issue.

Mark Gamis · Answer 9 · Sat Mar 02 2013 23:57:38 GMT+0800 (China Standard Time)

Thanks othree for the "fix". Looking forward to your AutoComplPop fork.

liuyicheng · Answer 10 · Thu Mar 07 2013 01:32:02 GMT+0800 (China Standard Time)

Thanks @othree for the "fix".
Or add this in your .vimrc is also useful:
filetype on
filetype plugin on