Disable automatic semantic completion for specific filetypes

[leigh-ols]

We used to be able to use the g:ycm_filetype_specific_completion_to_disable setting for this. However at some point the behavior has changed and this entirely disabled semantic completion for these filetypes even when pressing <C-Space>.

Where as previously it only disabled the automatic triggers.

How do I disable semantic completion automatic triggers for certain filetypes, while still allowing <C-Space> to continue working?

[bstaletic]

Use g:ycm_semantic_triggers.

let g:ycm_semantic_triggers = { 'c': [] }

[leigh-ols]

Correct me if i'm wrong but doesn't g:ycm_semantic_triggers only allow you to add more triggers and not remove them?

Setting key-value pairs on the dictionary adds semantic triggers to the
internal default set (listed below). You cannot remove the default triggers,
only add new ones.

I tried this before submitting the issue and:

let g:ycm_semantic_triggers = { 'php' : [] }

Does not work.

[leigh-ols]

Is there really no way to do this anymore?

This functionality used to exist.

[bstaletic]

g:ycm_semantic_triggers doesn't only add new triggers. Are you sure the variable has the expected value? Check with :echo g:ycm_semantic_triggers.

[leigh-ols]

In vimrc:

let g:ycm_semantic_triggers = { 'php' : [] }

In vim:

echo g:ycm_semantic_triggers
{'php': []}

Typing $this:: or $this-> still fires semantic completion.

let g:ycm_filetype_specific_completion_to_disable = { 'vim':1, 'txt':1, 'javascript':1, 'php':1 }
Disables semantic triggers, but also disables <C-Space> which some months back it didn't used to do.

g:ycm_semantic_triggers doesn't only add new triggers.

The documentation states otherwise, are the docs incorrect? Is this a bug?

[micbou]

let g:ycm_filetype_specific_completion_to_disable = { 'vim':1, 'txt':1, 'javascript':1, 'php':1 }
Disables semantic triggers, but also disables which some months back it didn't used to do.

The old behavior was not working as expected because there was no fuzzy-matching in that case. See issue #961. Pressing <C-Space> was the same as directly calling Vim's omnifunc through <C-X><C-O><C-P>. I think these changes should bring the old behavior back without the fuzzy-matching issue. Could you give it a try?

The documentation states otherwise, are the docs incorrect? Is this a bug?

No, the docs are correct but I think that being able to override the default triggers would be an improvement. However, this would break users adding custom triggers to the predefined ones so it's probably out of the question. Maybe we could add a new option with that behavior and deprecate g:ycm_semantic_triggers. We could name it g:ycm_filetype_triggers. @Valloric @puremourning @bstaletic @vheon Thoughts?

[bstaletic]

Okay, I was obviously wrong about g:ycm_semantic_triggers. I think the general idea of deprecating the current option in favour of g:ycm_filetype_triggers is good. We should probably :echom the deprecation warning too. I also really think we should start putting a "timer" on the deprecation period too.