Issue with members about deoplete-tag HOT 5 CLOSED

Thank you for the report.

I get the problem.

This feature is really needed? I think you should use LSP completion instead.

from deoplete-tag.

Hi @Shougo ,

Actually LSP would rely on clang based tools and the need of a JSON compilation database.
While it can be pretty straighforward to generate when using CMake or clang toolchain, it's not the case with classic Make/gcc projects (which I'm mostly working on)

So in my case ctags based completion is by far the most convenient which doesn't require any configuration. I can jump on any project, generate the tags (even for bash scriptss.... ) and I'm good to go. For sure it's not 100% perfect as it doesn't know actual defines used at compilation time but it does the job 99% of the time.

Assuming that omnicompletion can suggest members correctly using the tag file is there something really blocking to do it for deoplete ?

from deoplete-tag.

And by the way I'd be happy to contribute if you think the change is possible.

from deoplete-tag.

OK. But the change is not possible.

You should call the omnifunc from deoplete instead.

set completeopt+=noselect
call deoplete#custom#option('omni_patterns', {
\ 'c': ['[^. *\t]\%(\.\|->\)\w*',
\ 'cpp': ['[^. *\t]\%(\.\|->\)\w*', '[a-zA-Z_]\w*::'],
\})

from deoplete-tag.

Thanks @Shougo it fixes my problem.

from deoplete-tag.