Sep 9th, 2013
After my last trials with OmniCppComplete, exuberant-ctags, and similar vim plugins or packages I was really reluctant to restart this endeavor again and again with disappointment in the end.
While IDEs like Eclipse, Visual Studio, and XCode were getting stronger, my vim usage has degraded to plain text and short task single ﬁle editing where fewer magic was suﬃcient and the universal powers of vim most appropriate. Even then, I was often drawn to editors like Sublime Text 2 due to features like multi cursor and plugins like emmet.
Finally, my journey might have found an end! After reading this blog about Vim autocomplete on the web and watching a screencast on youtube, I charged enough energy to give it another try.
I basically followed mostly mentioned blog with the exception that I am using ultisnips instead of snip-mate because it simply worked better for me. I installed the bundles using the excellent pathogen, which also ﬁts nicely with my dotﬁles in my github repo.
In the end, I added the following bundles:
I am using these extensions now for quite a while and except for highly sophisticated tasks and huge projects, everything runs ﬁne out of the box. UltiSnips is actually turned out to be a killer feature - and is highly customisable.
The only ﬂaw I have found is that
clang_complete fails if the ﬁle path contains a white space character.
That’s it again and cheers!