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

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

Closed
markgamis opened this issue Aug 12, 2012 · 10 comments
Closed

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

markgamis opened this issue Aug 12, 2012 · 10 comments

Comments

@markgamis
Copy link

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.

@sukima
Copy link
Owner

sukima commented Aug 13, 2012

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.

@markgamis
Copy link
Author

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"

@malexandre
Copy link

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

@sukima
Copy link
Owner

sukima commented Oct 22, 2012

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
Copy link

othree commented Feb 6, 2013

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

In your vimrc

@sukima sukima closed this as completed Feb 7, 2013
@jonahx
Copy link

jonahx commented Feb 22, 2013

Thanks othree, I had the same problem and that worked

sukima added a commit that referenced this issue Feb 22, 2013
Added to announce the issue described in issue #15
@sukima
Copy link
Owner

sukima commented Feb 22, 2013

Added fix to README file.

@othree
Copy link

othree commented Feb 22, 2013

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.

@markgamis
Copy link
Author

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

@liuyicheng
Copy link

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

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

No branches or pull requests

6 participants