-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
No completions for STL classes (such as string) #305
Comments
Unable to reproduce. I took your test case and used YCM's You probably made a mistake in your extra conf file. |
Had the same problem for a while, I just figured it out : it's indeed a mistake in ycm_extra_conf.py but kind of a tricky one. Solution : Use c++11 or c++1y instead. |
Extends PreparedTriggers. Allows one to obtain the current trigger regex from inside semantic completers, enabling customized completions based on it, like normal code completion or argument hints. <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/valloric/ycmd/305) <!-- Reviewable:end -->
I'm on Ubuntu 13.04 using a custom-built vim.
I mostly followed the quick install instructions, except I opted to use the system libclang.
If I make a very simple file and use a simple .ym_extra_conf.py that's basically a copy, paste job from the YCM version and make the following file:
when I type "mystring." I get a "User defined completion (^U^N^P) Pattern not found" message printed to the status line:
Here is the output of :YcmDiags
Forcing compilation, this will block Vim until done.
No warnings or errors detected
Here is the output of :messages
"simple.cpp" 7L, 75C
No completions found; errors in file?
The simple completions seem to work, such as finishing "mystring" for me, but not the meaningful syntactic ones. I'm kind of at a loss as to how to debug this thing further since the output of YcmDiags suggests that the file is being built properly, and thus finding string.h on my system.
Any help is appreciated,
Kris
The text was updated successfully, but these errors were encountered: