You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tweekmonster
I have this config in my vimrc, but my deoplete is lazy loaded on Insert mode event. so when I open a cpp file, :Neomake clang still get errors about use of undeclared identifier 'nullptr', after I go into insert mode, :Neomake clang will not show issues, so I think the options below is detect when deoplete is loaded.
let g:deoplete#sources#clang#flags = ['--std=c++11']
let g:deoplete#sources#clang#autofill_neomake = 1
The text was updated successfully, but these errors were encountered:
wsdjeg
changed the title
options for this plugins should be detect when plugin is loaded.
options for this plugins should be detect when deoplete-clang2 is loaded.
Jan 29, 2017
@wsdjeg This is a problem I'm working on. All of the logic for gathering the flags are in the deoplete source. It needs to be moved to a reusable Python module, or ported to VimL and passed in via deoplete's context var.
Right now, the workaround is to first trigger InsertEnter.
@tweekmonster
I have this config in my vimrc, but my deoplete is lazy loaded on Insert mode event. so when I open a cpp file,
:Neomake clang
still get errors aboutuse of undeclared identifier 'nullptr'
, after I go into insert mode,:Neomake clang
will not show issues, so I think the options below is detect when deoplete is loaded.The text was updated successfully, but these errors were encountered: