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

Fail to call omni completion #2749

Closed
11 of 12 tasks
tenfyzhong opened this issue Aug 14, 2017 · 2 comments
Closed
11 of 12 tasks

Fail to call omni completion #2749

tenfyzhong opened this issue Aug 14, 2017 · 2 comments

Comments

@tenfyzhong
Copy link

Issue Prelude

Please complete these steps and check these boxes (by putting an x inside
the brackets) before filing your issue:

  • I have read and understood YCM's CONTRIBUTING document.
  • I have read and understood YCM's CODE_OF_CONDUCT document.
  • I have read and understood YCM's README, especially the
    Frequently Asked Questions section.
  • I have searched YCM's issue tracker to find issues similar to the one I'm
    about to report and couldn't find an answer to my problem. (Example Google
    search.
    )
  • If filing a bug report, I have included the output of vim --version.
  • If filing a bug report, I have included the output of :YcmDebugInfo.
  • If filing a bug report, I have attached the contents of the logfiles using
    the :YcmToggleLogs command.
  • If filing a bug report, I have included which OS (including specific OS
    version) I am using.
  • If filing a bug report, I have included a minimal test case that reproduces
    my issue, including what I expected to happen and what actually happened.
  • If filing a installation failure report, I have included the entire output
    of install.py (or cmake/make/ninja) including its invocation
  • I understand this is an open-source project staffed by volunteers and
    that any help I receive is a selfless, heartfelt gift of their free time. I
    know I am not entitled to anything and will be polite and courteous.
  • I understand my issue may be closed if it becomes obvious I didn't
    actually perform all of these steps.

Thank you for adhering to this process! It ensures your issue is resolved
quickly and that neither your nor our time is needlessly wasted.

Issue Details

summary:

Fail to call omni completion.
A good commit: 263bd88

  • What did you do?

When I type <c-x><c-o>, vim exist to normal mode.

  • What did you expect to happen?

Include description of the expected behaviour.
And I found a good commit: 263bd88
here's a screenshot: https://asciinema.org/a/h1fxrkl299DvkVuRj37O3XWZv

  1. Checkout to 263bd88
  2. edit haha.c
  3. type <c-x><c-o> to call omni completion

The function signature is appeared.
I expect the behaviour like this screenshot.

  • What actually happened?

Fail to call omni completion when I type <c-x><c-o>.
Here is a screenshot: https://asciinema.org/a/HTiPjqHZeBaFEnWYm6J6OI3oD

Diagnostic data

Output of vim --version

https://gist.github.com/bd0582c9a4f6af08263b18fcf7be61fc

Output of YcmDebugInfo

https://gist.github.com/129614b6304d6dd144fd6170e4b1aeb8

Contents of YCM, ycmd and completion engine logfiles

Include link here to a gist containing the entire logfiles for ycm, ycmd
and any completer logfiles listed by :YcmToggleLogs.
https://gist.github.com/tenfyzhong/7fde72b5bb68b2b401365156c7198056

OS version, distribution, etc.

osx 10.10.5

Output of build/install commands

Include link to a gist containing the invocation and entire output of
install.py if reporting an installation issue.

@bstaletic
Copy link
Collaborator

Since #2657 YCM doeesn't use 'omnifunc'. Completion like you expect is available if you press <C-Space>.

@micbou
Copy link
Collaborator

micbou commented Aug 14, 2017

Duplicate of #2735.

@micbou micbou closed this as completed Aug 14, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 21, 2021
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