You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've some issues with this plugin on my Vim. I've installed it with the Vundle plugin manager for Vim, and linked the good folder for clang libs.
For the first issue, when I insert several includes on the top of my .cpp files, only the first is used to autocomplete the std:: word. So, if I include cmath as first, only cmath's functions will appears, and if I include iostream as first, only functions as cout or cin appears, and not cos or abs.
Secondly, when I include vector or map for example, I always finished with a pattern not found when I try to autocomplete a vector object, and the autocomplete menu doesn't show the vector class when I type std:: unlike with the iostream header for example.
Any suggestions about this ?
Olivier
The text was updated successfully, but these errors were encountered:
I've noticed similar issue as @Olivier-Delierre. When I configured clang_complete it doesn't suggest function names such as push_back, size etc. on vector objects. I'm not sure if it is capable of doing so but I was expecting such behaviour.
Hello,
I've some issues with this plugin on my Vim. I've installed it with the Vundle plugin manager for Vim, and linked the good folder for clang libs.
For the first issue, when I insert several includes on the top of my .cpp files, only the first is used to autocomplete the
std::
word. So, if I includecmath
as first, only cmath's functions will appears, and if I includeiostream
as first, only functions ascout
orcin
appears, and notcos
orabs
.Secondly, when I include vector or map for example, I always finished with a
pattern not found
when I try to autocomplete a vector object, and the autocomplete menu doesn't show the vector class when I typestd::
unlike with theiostream
header for example.Any suggestions about this ?
Olivier
The text was updated successfully, but these errors were encountered: