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
The text was updated successfully, but these errors were encountered:
Ram-Z
changed the title
ale_cpp_options should be ignored when ale_c_parse_compile_commands = 1
ale_cpp_{gcc,clang}_options should be ignored when ale_c_parse_compile_commands = 1
Dec 31, 2019
Almost all C/C++ issues with flags should now be discussed in #3276, so a comprehensive solution can be found for most people, for automatically detecting flags.
When the compile flags are being read from a compilation database, ALE should'n override them by appending
ale_cpp_options
to the end.Obviously one could simply
let g:ale_cpp_options = ''
, but that prevents setting sane defaults when a compilation database cannot be found.There should still be the ability to add additional options even if a compilation database is found.
I propose to split the variables into two
ale_cpp_options
andale_cpp_extra_options
and have something like this inale_linters/cpp/{gcc,clang}.vim
.The text was updated successfully, but these errors were encountered: