blocks|key|1112651|text|我觉得这应该比它更容易的原因之一，因为-输出-替换-xml本质上给了我我想要的答案，它只是不给我一个简单的消费方式。但是，由于输出(如果不需要替换)是非常可预测的，所以解析输出并不太困难。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1112652|我现在拥有的是|1112653|clang-format+-style=file+-output-replacements-xml+%7C+grep+-c+"<replacement+"+>/dev/null|code-block|syntax|javascript|1112654|这实际上返回了我想要的退出代码的逆值，因为grep返回0(如果匹配)，1(如果没有匹配)。但这是很容易处理的。|1112655|所以我的git预提交钩子的相关部分应该是|1112656|git+diff+--cached+--name-only+--diff-filter=ACMRT+%7C
++grep+"\.[cmh]$"+%7C
++xargs+-n1+clang-format+-style=file+-output-replacements-xml+%7C
++grep+"<replacement+"+>/dev/null
if+[+$?+-ne+1+];+then+
++++echo+"Commit+did+not+match+clang-format"
++++exit+1
fi|1112657|获取索引中文件的完整文件名(不包括正在删除的文件和其他我可能不想处理该文件的异常情况)。|ordered-list-item|1112658|只保留我要检查的东西的文件名(在我的例子中，只有c、m和h文件)|1112659|通过xargs运行结果，从本质上“针对每个”下一个命令|1112660|在所有文件上运行clang格式和输出替换-xml选项。|1112661|搜索替换(相对于替换)，这表明clang-格式已经找到了它想要做的替换。(放弃所有输出，因为XML对用户没有意义。)|1112662|最后一个命令退出1+(grep说我们什么也没有发现)，我们已经做好了，一切都很好。|1112663|如果没有，则显示一条消息并退出1，这将取消提交。不幸的是，我们没有一种简单的方法来告诉用户哪个文件是问题所在，但是他们可以自己运行clang格式并查看。|1112664|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|17|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|18|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|19|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|Q|7|1B|8|@]|9|@]|A|$]]|$1|R|3|S|5|Q|7|1C|8|@]|9|@]|A|$]]|$1|T|3|U|5|Q|7|1D|8|@]|9|@]|A|$]]|$1|V|3|W|5|Q|7|1E|8|@]|9|@]|A|$]]|$1|X|3|Y|5|Q|7|1F|8|@]|9|@]|A|$]]|$1|Z|3|10|5|Q|7|1G|8|@]|9|@]|A|$]]|$1|11|3|12|5|Q|7|1H|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|14|$]]

One of the reasons I feel like this should be easier than it is because -output-replacements-xml essentially gives me the answer that I want, it just doesn't give it to me in an easy to consume way. However, since the output if no replacements are needed is very predictable, parsing the output isn't too hard.

What I have right now is 

<pre><code>clang-format -style=file -output-replacements-xml | grep -c "&lt;replacement " &gt;/dev/null
</code></pre>

This actually returns the inverse of the exit code I want, since grep returns 0 if something matches, 1 if nothing does. But that is easy enough to deal with.

So the relevant bit of my git pre-commit hook would be

<pre><code>git diff --cached --name-only --diff-filter=ACMRT |
 grep "\.[cmh]$" |
 xargs -n1 clang-format -style=file -output-replacements-xml |
 grep "&lt;replacement " &gt;/dev/null
if [ $? -ne 1 ]; then 
 echo "Commit did not match clang-format"
 exit 1
fi
</code></pre>

<ol>
<li>Get the full filenames of the files in the index (excluding files that are being deleted and other unusual cases where I might not want to process the file)</li>
<li>Only keep the filenames of things I want to check the formatting of (in my case just c,m, and h files)</li>
<li>Run the results through xargs to essentially "for each" the next command</li>
<li>Run clang-format with the -output-replacements-xml option on all of the files</li>
<li>Search for replacement (as opposed to replacements) that indicates that clang-format has found a replacement that it wants to make. (Discarding all output as the XML won't be meaningful to the user.)</li>
<li>The last command exits 1 (grep says we found nothing) we are done and things are fine.</li>
<li>If not, display a message and exit 1, which cancels the commit. Unfortunately we don't have an easy way to tell the user which file was the problem, but they can run clang-format themselves and see.</li>
</ol>

blocks|key|1833014|text|我不完全确定您的用例是什么，但是请查看git+(https://llvm.org/svn/llvm-project/cfe/trunk/tools/clang-format/git-clang-format)。它基本上为git提供了clang格式的集成，也许这就是您所要寻找的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1833015|entityMap|0|LINK|mutability|MUTABLE|url|https://llvm.org/svn/llvm-project/cfe/trunk/tools/clang-format/git-clang-format^0|O|27|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I am not entirely sure what your use case is, but check out git-clang-format (<a href="https://llvm.org/svn/llvm-project/cfe/trunk/tools/clang-format/git-clang-format" rel="noreferrer">https://llvm.org/svn/llvm-project/cfe/trunk/tools/clang-format/git-clang-format</a>). It basically provides a clang-format integration for git and maybe that is what you are looking for.

blocks|key|1112729|text|我使用git-clang-format和Mike博客中的预提交脚本：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1112730|#!/bin/python

import+subprocess
output+=+subprocess.check_output(["git",+"clang-format",+"--diff"])

if+output+not+in+['no+modified+files+to+format\n',+'clang-format+did+not+modify+any+files\n']:
++++print+"Run+git+clang-format,+then+commit.\n"
++++exit(1)
else:
++++exit(0)|code-block|syntax|javascript|1112731|这个脚本有一个小错误，因为当没有提交时，它就不能工作(试图对照还不存在的头进行检查)。若要绕过此操作，请使用-n或--no-verify选项。|1112732|使用-n跳过预提交脚本对于绕过检查也是有帮助的，因为大型代码库需要很长的时间。|1112733|最初的帖子在这里：http://www.dx13.co.uk/articles/2015/4/3/Setting-up-git-clang-format.html|1112734|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dx13.co.uk/articles/2015/4/3/Setting-up-git-clang-format.html^0|3|G|0|0|1I|2|1L|B|0|2|2|0|9|20|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1A|8|@]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|Q|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

I use <code>git-clang-format</code> and a pre-commit script from Mike Rhodes' blog:

<pre><code>#!/bin/python

import subprocess
output = subprocess.check_output(["git", "clang-format", "--diff"])

if output not in ['no modified files to format\n', 'clang-format did not modify any files\n']:
 print "Run git clang-format, then commit.\n"
 exit(1)
else:
 exit(0)
</code></pre>

The script has a small error in that it doesn't work when there are no commits (trying to check against HEAD which doesn't exist yet). To bypass this, use the <code>-n</code> or <code>--no-verify</code> option.

Using <code>-n</code> to skip the pre-commit script can also be helpful when you what to bypass the check because it can take a long time for a large codebase.

The original post is here: <a href="http://www.dx13.co.uk/articles/2015/4/3/Setting-up-git-clang-format.html" rel="nofollow">http://www.dx13.co.uk/articles/2015/4/3/Setting-up-git-clang-format.html</a>

blocks|key|1833096|text|在受到戴维·奥格伦的职位的启发后，我制作了一个pre-commit钩子，它能够处理阶段性的更改。这将确保pre-commit钩子能够在实际构成提交内容的代码上工作，并且不会被没有被分阶段的clang-format运行所愚弄。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1833097|#!/bin/bash

files=()
for+file+in+`git+diff+--cached+--name-only+--diff-filter=ACMRT+%7C+grep+-E+"\.(cpp%7Chpp)$"`;+do
++if+!+cmp+-s+<(git+show+:${file})+<(git+show+:${file}%7Cclang-format);+then
++++files%2B=("${file}")
++fi
done

if+[+-n+"${files}"+];+then
echo+Format+error+within+the+following+files:
printf+"%25s\n"+"${files[@]}"
exit+1
fi|code-block|syntax|javascript|1833098|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/22866610/25782^0|N|A|1G|A|2M|C|3|9|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

After I got inspired by <a href="https://stackoverflow.com/a/22866610/25782">David Ogren's post</a> I made a <code>pre-commit</code> hook that is able to work on the staged changes. This will ensure that the <code>pre-commit</code> hook will work on the code that will actual make up the content of the commit and can't be fooled by a <code>clang-format</code> run that didn't get staged.

<pre><code>#!/bin/bash

files=()
for file in `git diff --cached --name-only --diff-filter=ACMRT | grep -E "\.(cpp|hpp)$"`; do
 if ! cmp -s &lt;(git show :${file}) &lt;(git show :${file}|clang-format); then
 files+=("${file}")
 fi
done

if [ -n "${files}" ]; then
echo Format error within the following files:
printf "%s\n" "${files[@]}"
exit 1
fi
</code></pre>

blocks|key|1112806|text|我稍微调整了小灵通在本文中的评论以得到如下结果：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1112807|find+embedded/+-regex+'.*\.$ino\%7Ccpp\%7Chpp\%7Ccc\%7Ccxx\%7Ch$'+-exec+cat+{}+\;+%7C+diff+-u+<(find+embedded/+-regex+'.*\.$ino\%7Ccpp\%7Chpp\%7Ccc\%7Ccxx\%7Ch$'+-exec+clang-format-3.9+-style=file+{}+\;)+-|style|CODE|1112808|那就是..。|1112809|cat所有cpp-ish文件并将其输送到diff+(diff将接受stdin，因为我在最后指定了-+)。|ordered-list-item|1112810|使用进程替换(+<(+..+)语法)对这些相同的文件运行clang-format。这里不要使用就地格式化。这是发送给diff的另一半|1112811|如果diff没有输出就退出，那么成功！你也可以通过$?检查出口代码--应该是零。|1112812|我让我的CI服务(travis)在bash脚本中运行这一行，以确保格式化正确。我有另一个脚本来实际运行格式化程序。这让我想起了一个警告:您必须使用一个可以执行process+(posix外壳不)的shell。|1112813|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/22866609/can-clang-format-tell-me-if-formatting-changes-are-necessary/50264116#comment63404587_22866610|1|https://unix.stackexchange.com/a/17112/89502^0|6|A|0|0|0|57|0|0|0|3|K|4|Q|4|X|5|1C|1|0|8|7|S|C|1M|4|0|2|4|P|2|0|2G|8|1|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@$A|17|B|18|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|1A|8|@$A|1B|B|1C|F|G]|$A|1D|B|1E|F|G]|$A|1F|B|1G|F|G]|$A|1H|B|1I|F|G]|$A|1J|B|1K|F|G]]|9|@]|C|$]]|$1|M|3|N|5|L|7|1L|8|@$A|1M|B|1N|F|G]|$A|1O|B|1P|F|G]|$A|1Q|B|1R|F|G]]|9|@]|C|$]]|$1|O|3|P|5|L|7|1S|8|@$A|1T|B|1U|F|G]|$A|1V|B|1W|F|G]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1X|8|@]|9|@$A|1Y|B|1Z|1|20]]|C|$]]|$1|S|3|-4|5|6|7|21|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

I slightly adjusted the <a href="https://stackoverflow.com/questions/22866609/can-clang-format-tell-me-if-formatting-changes-are-necessary/50264116#comment63404587_22866610">comment from phs in this post</a> to come up with:

<code>find embedded/ -regex '.*\.$ino\|cpp\|hpp\|cc\|cxx\|h$' -exec cat {} \; | diff -u &lt;(find embedded/ -regex '.*\.$ino\|cpp\|hpp\|cc\|cxx\|h$' -exec clang-format-3.9 -style=file {} \;) -
</code>

that is..

<ol>
<li><code>cat</code> all cpp-ish files and pipe that to <code>diff</code> (<code>diff</code> will accept <code>stdin</code> because I specify <code>-</code> at the end)</li>
<li>use process substitution (the <code>&lt;( .. )</code> syntax) to run <code>clang-format</code> on those same files. Don't use in-place formatting here. This is the other half that's sent to <code>diff</code></li>
<li>if <code>diff</code> exits with no output, success! You can also check the exit code via <code>$?</code> -- it should be zero. </li>
</ol>

I have my CI service (travis) run this line in a bash script to make sure things are formatted properly. I have another script for actually running the formatter in-place. This reminds me of a caveat: you must use a shell that can do process sub (<a href="https://unix.stackexchange.com/a/17112/89502">the posix shell does not</a>).

blocks|key|2111596|text|run-clang格式是clang-format的一个简单包装器，它的设计精确地被用作钩子或连续集成脚本:它输出一个差异并以合理的状态退出。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2111597|主页上给出的例子说明了这一点：|2111598|​|2111599|📷|atomic|2111600|2111601|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Sarcasm/run-clang-format|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/776425be2ae859d82132b899345a0f86.png|imageAlt^0|C|C|0|B|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@$9|14|A|15|1|16]]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|18|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|19|8|@]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|M|3|I|5|6|7|1D|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|W|R|X|E|$Y|Z|10|-4]]]]

<a href="https://github.com/Sarcasm/run-clang-format" rel="noreferrer">run-clang-format</a> is a simple wrapper around <code>clang-format</code> designed precisely to be used as a hook or as a continuous integration script: it outputs a diff and exits with a sensible status.

The example given on the home page speaks for itself:

<a href="https://raw.githubusercontent.com/Sarcasm/run-clang-format/master/screenshot.png" rel="noreferrer"><img src="https://raw.githubusercontent.com/Sarcasm/run-clang-format/master/screenshot.png" alt="run-clang-format example"></a>

blocks|key|1112858|text|从clang-form-10开始，您可以使用--dry-run和-Werror命令行选项。它们将导致ClangFormat将任何格式冲突输出到stdout，并在任何输入文件未正确格式化的情况下返回非零退出状态。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1112859|$+clang-format+--dry-run+--Werror+foo.cpp
foo.cpp:129:23:+error:+code+should+be+clang-formatted+[-Wclang-format-violations]
++++++++if+(rc+<=+0)+{
$+echo+$?
1|code-block|syntax|javascript|1112860|来自我的网站：https://rigtorp.se/notes/clang-format/|1112861|entityMap|0|LINK|mutability|MUTABLE|url|https://rigtorp.se/notes/clang-format/^0|M|9|W|7|0|0|7|12|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|M|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

Starting with clang-format-10, you can use the <code>--dry-run</code> and <code>-Werror</code> command line options. They will cause ClangFormat to output any formatting violations to stdout and return a non-zero exit status if any input file was not correctly formatted.
<pre><code>$ clang-format --dry-run --Werror foo.cpp
foo.cpp:129:23: error: code should be clang-formatted [-Wclang-format-violations]
 if (rc &lt;= 0) {
$ echo $?
1
</code></pre>
Originally from my website here: <a href="https://rigtorp.se/notes/clang-format/" rel="nofollow noreferrer">https://rigtorp.se/notes/clang-format/</a>

blocks|key|1833232|text|命令行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1833233|您可以使用git+diff和clang-format-diff|offset|length|style|CODE|1833234|$+git+diff+-U0+--no-color+--staged+HEAD+%7C+clang-format-diff+-p1|code-block|syntax|javascript|1833235|注意：|1833236|--staged仅用于在阶段性更改上运行clang-format-diff。|unordered-list-item|1833237|如果要在特定目录上运行此命令，可以将其重写为：|1833238|$+git+diff+-U0+--no-color+--staged+HEAD+--+$PWD/dir1+$PWD/dir2+$PWD/dir3++%7C+clang-format-diff+-p1|1833239|..and+the+pre-commit|1833240|现在你的预提交可以是这个：|1833241|#!/bin/bash

dir_list="$PWD"++#+Add+the+directories+you+want+here
cmd="git+diff+-U0+--no-color+--staged+HEAD+--+$dir_list+%7C+clang-format-diff+-p1"

echo+""
echo+"Running+clang-format+on+this+commit"
echo+""

#+Execute+the+format+command
diff=$(eval+"$cmd")
if+[[+$?+-ne+0+]]
then
++++echo+"Command+failed+to+execute."
++++exit+1
fi

#+Print+the+outcome
if+[[+-z+"$diff"+]]
then
++++echo+"Everything+is+clean"
++++exit+0
else
++++echo+"$diff"
++++echo+""
++++echo+"Commit+aborted+due+to+code+format+inconsistencies."
++++exit+1
fi|1833242|entityMap^0|0|5|8|E|H|0|0|0|0|8|K|H|0|0|0|A|A|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@$D|15|E|16|F|G]|$D|17|E|18|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|19|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1A|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1B|8|@$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|R|3|S|5|Q|7|1G|8|@]|9|@]|A|$]]|$1|T|3|U|5|J|7|1H|8|@]|9|@]|A|$K|L]]|$1|V|3|W|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Z|3|10|5|J|7|1M|8|@]|9|@]|A|$K|L]]|$1|11|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|12|$]]

<h2>Command Line</h2>
You can use <code>git diff</code> along with <code>clang-format-diff</code>:
<pre class="lang-sh prettyprint-override"><code>$ git diff -U0 --no-color --staged HEAD | clang-format-diff -p1
</code></pre>
Note:
<ul>
<li><code>--staged</code> is used to run <code>clang-format-diff</code> only on the staged changes</li>
<li>If you want to run this command on specific directories, you can rewrite it as:</li>
</ul>
<pre><code>$ git diff -U0 --no-color --staged HEAD -- $PWD/dir1 $PWD/dir2 $PWD/dir3 | clang-format-diff -p1
</code></pre>
<h2>..and the <code>pre-commit</code></h2>
Now you pre-commit can be this one:
<pre class="lang-sh prettyprint-override"><code>#!/bin/bash

dir_list=&quot;$PWD&quot; # Add the directories you want here
cmd=&quot;git diff -U0 --no-color --staged HEAD -- $dir_list | clang-format-diff -p1&quot;

echo &quot;&quot;
echo &quot;Running clang-format on this commit&quot;
echo &quot;&quot;

# Execute the format command
diff=$(eval &quot;$cmd&quot;)
if [[ $? -ne 0 ]]
then
 echo &quot;Command failed to execute.&quot;
 exit 1
fi

# Print the outcome
if [[ -z &quot;$diff&quot; ]]
then
 echo &quot;Everything is clean&quot;
 exit 0
else
 echo &quot;$diff&quot;
 echo &quot;&quot;
 echo &quot;Commit aborted due to code format inconsistencies.&quot;
 exit 1
fi

</code></pre>

blocks|key|1112904|text|只需使用-n选项即可|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1112905|clang-format+-n+<file>|code-block|syntax|javascript|1112906|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can simply use the -n option
<pre><code>clang-format -n &lt;file&gt;
</code></pre>

Is there an way that you can run <code>clang-format</code> in a mode where it reports if the file meets the specified format? A kind of dry-run mode where it reports if a change is needed, but doesn't make the change. Ideally I'd like clang-format to just return a non-zero exit code if the file needs changes. Or, even more ideally, a non-zero exit code and a list of the files that need changes on standard output.

I'm trying to keep the question generic, so that more people can answer, but what I am trying to do is write a git pre-commit hook that will reject any commits that don't match the expected .clang-format . It's easy to run clang-format on the list of files in the index. But it's hard to know if clang-format actually changed anything. 

I have one potential solution based on <code>-output-replacements-xml</code> (that I will post as an answer), but it's a hack and I feel like this should be more straightforward. Comments/suggestions, edits, different answers/approaches are all welcome.

Can clang-format tell me if formatting changes are necessary?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如果文件符合指定格式，您是否可以以clang-format的模式运行它报告的方式？一种模拟运行模式，在这种模式中，它报告是否需要更改，但不进行更改。理想情况下，如果文件需要更改，我希望clang格式只返回一个非零退出代码。或者，更理想的情况是，非零退出代码和需要对标准输出进行更改的文件列表。我试图保持这个问题的一般性，...

问clang-格式能告诉我是否需要修改格式吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问clang-格式能告诉我是否需要修改格式吗？EN