7d72519039
[READY] Do not disable omnifunc when filetype completion is disabled Prior to PR https://github.com/Valloric/YouCompleteMe/pull/2657, it was possible to trigger Vim's omnifunc with `<C-Space>` even if semantic completion was disabled for the current filetype through the `g:ycm_filetype_specific_completion_to_disable` option. It worked because `<C-Space>` was mapped to `<C-X><C-O><C-P>`, which are the keys to trigger the omnifunc. PR https://github.com/Valloric/YouCompleteMe/pull/2657 changed that by making `<C-Space>` directly call the `SendCompletionRequest` function with `force_semantic` sets to `True`. This change was necessary to get fuzzy matching with the omnifunc (see issue https://github.com/Valloric/YouCompleteMe/issues/961) but broke the `<C-Space>` behavior when filetype completion is disabled. This PR restores that behavior. Fixes https://github.com/Valloric/YouCompleteMe/issues/2950. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/valloric/youcompleteme/2978) <!-- Reviewable:end --> |
||
|---|---|---|
| .. | ||
| client | ||
| tests | ||
| __init__.py | ||
| base.py | ||
| buffer.py | ||
| diagnostic_filter.py | ||
| diagnostic_interface.py | ||
| omni_completer.py | ||
| paths.py | ||
| setup.py | ||
| syntax_parse.py | ||
| unsafe_thread_pool_executor.py | ||
| vimsupport.py | ||
| youcompleteme.py | ||
