<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Don,</p>
<p>there is a `-export-fixes` option that will serialize the
diagnostics and fixits into yaml (machine readable, but same
content).<br>
Otherwise you would need to capture the logs, e.g. using `tee` and
piping in linux for interactive clang-tidy usage.</p>
<p>Best Regards, Jonas<br>
</p>
<div class="moz-cite-prefix">Am 29.03.19 um 20:51 schrieb Don Hinton
via cfe-dev:<br>
</div>
<blockquote type="cite"
cite="mid:CAL2T-v6Hvbzitap950JtkyFnjgouxSdZ38SU2CebAqJGTJ6pnw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Is there a way to view a clang-tidy export file
that will show the original warning+fixit as it appeared in the
original clang-tidy output?<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
cfe-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a>
` o</pre>
</blockquote>
</body>
</html>