.clang-format file isn't used

[viveksjain]

Running on Ubuntu 14.04, VSCode 1.10.2 and C++ extension 0.10.5. I seem to be having a similar issue to #196 - the flags passed to clang-format are
-style={ BasedOnStyle: LLVM, UseTab: Never, IndentWidth: 2, BreakBeforeBraces: Allman, AllowShortIfStatementsOnASingleLine: false, IndentCaseLabels: false, ColumnLimit: 0 } -fallback-style=LLVM
which means my actual .clang-format file is not used (should be -style=file). Where is this other style coming from and how can I fix it?

[viveksjain]

Just found #536 which is tangentially (but not exactly) related. It also says that issue is supposed to be fixed in 0.10.4, but my later version is still having this issue.

[viveksjain]

Manually specifying the dict for C_Cpp.clang_format_style works, but setting it to "file" doesn't work.

[sean-mcmanus]

It's #571 , but I think we'll use this bug to track the issue, since the other bug mostly discusses another issue that I couldn't repro.

[Binero]

Can confirm this. Just running clang-format from the terminal works fine, VSC ignores it and always uses the fallback.

[rooomaa]

same on ubuntu-16.04 & rhel-7.3 + vscode 1.11.1

[sean-mcmanus]

The workaround is to change your clang_format_fallbackStyle to one of the non-"Visual Studio" presets, such as LLVM. But hopefully this will get fixed soon anyway.

[spencersutton]

The workaround is to change your clang_format_fallbackStyle to one of the non-"Visual Studio" presets, such as LLVM. But hopefully this will get fixed soon anyway.

That doesn't work for me but setting C_Cpp.clang_format_path to my system version of clang-format fixes it on macOS.

[sean-mcmanus]

@spencersutton Ah, that's probably because your .clang-format has newer fields that aren't supported by the 3.8 version we ship, i.e. different root cause from the Linux/Mac-only issue.

[spencersutton]

@sean-mcmanus You're right, I generated my .clang-format with clang-format --dump-config using my system clang-format. I found the version installed by vscode and ran it and got an error. There's no feedback in vscode if there's an error though.

It does work with default settings if I take the new option out.