Closed bchretien closed 9 years ago
Gotcha, working on this now.
Very simple fix, imho. Just checking if g:ycm_extra_conf_vim_data
exists.
Lemme know how it works for you.
Thanks for looking into it ;-)
Now I have:
function cmake#augroup#on_file_type..<SNR>59_render_for_cpp..cmake#flags#inject..cmake#flags#inject_to_syntastic, line 1
Vim(if):E716: Key not present in Dictionary: syntastic != 1 | return | endif
Error occured while executing "open" action!
Apparently, g:cmake_inject_flags = {}
, which could probably explain the previous YCM error as well. I checked some of the other variables that appear in set_options, and some are not the default ones (e.g. gcc/g++
for the compilers, RelWithDebInfo
for the build type, which could have been set from a pre-existing build
directory I presume).
Right, those are meant to be redefined with one's preferences. But in the event one would want to reconfigure an existing build directory from scratch, like deleting build
then recreating build
, I'd see why you'd want something like that.
Running cmake
with extra configuration variables is a little broken in the plugin (still working on this for a 0.5.0
release) but it sounds like that would help.
But g:cmake_inject_flags
should never be empty.
Version 0.5.0 should fix these issues. Re-open if you get more issues, thanks!
I removed YCM recently, and I get the following errors when entering a C++ file:
I guess you could test cmake.vim without YCM installed to track those errors.