Tobias Grosser

This commit drafts this feature. https://github.com/tobig/clang_complete/commit/3fe5c08f950caae0c9d49985823f97c84a005254 It is still a huge hack and currently also still very costly as we call clang at each character stroke. We can probably make...

There is also a feature called '' 'refresh': 'always'" see ':help complete-functions', which might be helpful here too.

I am currently not working on this, but please feel free to pick this up.

On 02/28/2013 01:55 AM, aliak00 wrote: > Hi, > > Having some trouble on Mountain Lion with clang_complete. Setup is: > vim 7.3 (+python but -python3) > clang 4.2 You...

On 03/03/2013 03:45 PM, thonguyen wrote: > I have the same problem. My system is gentoo, vim 7.3.409 built with python support, clang 3.2. > When I don't set g:clang_library_path,...

On 22.10.2014 20:38, balajij81 wrote: > Any help is much appreciated. No idea by just from looking at the stack trace. Maybe you do some print() debugging to see how...

As you realized this causes security concerns. A solution to address these concerns is to introduce a new argument to clang_complete-auto_user_options, which is called '.clang_complete-dynamic', which has the behaviour you...

This completion works for me. """ #include int foo() { std:: } """ What exactly is the file you are trying to complete? Can you set g:clang_debug=1, do a completion...

I think it would be unfortunate to require everybody to compile their own vim versions. This adds a lot of overhead, for a very limited benefit. My vim version supports...

On 02/19/2013 08:16 AM, Xavier Deguillard wrote: > In the last commit, I've pushed nearly all the code into the threads. The completion is also done asynchronously, and so nothing...