The linter generates .plist files again about ale HOT 2 OPEN

I played around with the ale_linters/c/clangcheck.vim and I can confirm that if the the same arguments are used if the build directory is detected, the .plist files are not created anymore:

    return '%e -analyze %s'
    \   . (empty(l:build_dir) ? ' --extra-arg=-Xclang --extra-arg=-analyzer-output=text --extra-arg=-fno-color-diagnostics': '')
    \   . ale#Pad(l:user_options)
    \   . (!empty(l:build_dir) ? '--extra-arg=-Xclang --extra-arg=-analyzer-output=text --extra-arg=-fno-color-diagnostics -p ' . ale#Escape(l:build_dir) : '')

That is obviously a hack, but someone who knows what is really going on could probably either code it clean or explain the observed behavior. I just copied the arguments without really knowing how clang-check works or even VimScript at all.

But hopefully this still helps.

from ale.

One way to fix that would be to add those arguments unconditionally:

    return '%e -analyze %s'
    \   . ' --extra-arg=-Xclang --extra-arg=-analyzer-output=text --extra-arg=-fno-color-diagnostics'
    \   . ale#Pad(l:user_options)
    \   . (!empty(l:build_dir) ? ' -p ' . ale#Escape(l:build_dir) : '')

As a workaround you can set the following in your config:

let g:ale_c_clangcheck_options =  ' --extra-arg=-Xclang --extra-arg=-analyzer-output=text --extra-arg=-fno-color-diagnostics'

from ale.