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

Completion disappears after entering anything after : for erlang #862

Closed
sedrik opened this issue Mar 3, 2014 · 3 comments
Closed

Completion disappears after entering anything after : for erlang #862

sedrik opened this issue Mar 3, 2014 · 3 comments

Comments

@sedrik
Copy link

sedrik commented Mar 3, 2014

My suspicion is that this a issue with the vimerl's omnicomplet function but I would like some assistance verifying and debugging this from YMC's point of view in order to do a proper error report to the vimerl project.

Here is a video showcasing the issue.
https://asciinema.org/a/8001

How would YMC expect a omnicomplete function to work when continuing to enter characters?

@ojung
Copy link

ojung commented May 14, 2014

I'm also looking for a fix for this.

For the moment I am forcing the semantic completion with <C-Space>. I have to type at least one character after the : for it to work, though.

@Valloric
Copy link
Member

How would YMC expect a omnicomplete function to work when continuing to enter characters?

YCM expects the omnifunc to adhere to the behavior described by :h complete-functions in Vim. That's about it. It might be that vimerl's omnifunc is expecting to be called on every keystroke; if it is, it shouldn't be doing that.

Try putting let g:ycm_cache_omnifunc = 0 in your vimrc and see if it works better. If that fixes it, vimerl's omnifunc doesn't work the way it should and using it with g:ycm_cache_omnifunc = 0 will unnecessarily slow down things.

Then again, there might also be an issue in YCM with auto-triggering on Erlang code, but this seems less likely.

@Valloric Valloric reopened this May 15, 2014
@sedrik
Copy link
Author

sedrik commented May 16, 2014

Yeah that was the issue, ignoring the let g:ycm_cache_omnifunc = 0 renders the expected behaviour.

I will report this to the vimerl.

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

No branches or pull requests

3 participants