clang_complete icon indicating copy to clipboard operation
clang_complete copied to clipboard

feature request: Header file completion

Open htfy96 opened this issue 10 years ago • 3 comments

After two years I switched back to clang_complete from ycm due to its size. What made me upset two years before was that no header file completion had been provided, and it seems that after two years there is still no support for this feature. Since I'm not alone with this request (http://stackoverflow.com/questions/26727765/make-clang-complete-autofill-header-files-is-it-possible), I opened this issue. The completion after #include < could be quite helpful when you cannot remember the exact file name(which is frequent when using boost library), which might be one of the killer features of ycmd. It would be better if this feature is provided. Thanks for your great work :+1:

htfy96 avatar Dec 30 '15 09:12 htfy96

In two years the project hasn't seen much development... And I'm not sure there was any intention to add this kind of completion to clang_complete at all. That said, I like such completion, so I have a plugin to which I just added code to pick up include paths from configuration of clang_complete. You might want to give it a try and see if it works for you.

xaizek avatar Dec 30 '15 09:12 xaizek

@xaizek Great. It works well for deoplete completion framework in neovim with g:inccomplete_showdirs set. The only thing I have to modify is:

let g:deoplete#omni#input_patterns.cpp = ['[^. *\t]\.\w*', '[^. *\t]\::\w*', '[^. *\t]\->\w*', '[<"].*/']
// Add the last one, otherwise `<../` and `"../` won't trigger omnifunc

This configuration also works for neocomplete, I think this should be included in the official doc of that plugin.

htfy96 avatar Dec 30 '15 10:12 htfy96

@htfy96, thanks for the feedback, updated the docs.

xaizek avatar Dec 30 '15 11:12 xaizek