<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">Yes, that is what I've settled on--placing the .clang-format file outside of the source-code tree, and doing something like:<br class=""><br class="">sourcecode/...<br class="">option-a/.clang-format<br class="">option-b/.clang-format<br class="">option-c/.clang-format<br class=""><br class="">Somebody then asked me to send them the 'option-c' format so they could run it on their code base. Unfortunately, he placed the '.clang-format' file in the wrong place, ran clang-format, and received an output they thought was 'option-c' but really wasn't. If instead he could have run something like:<br class=""><br class="">clang-format -style=custom:option-c ...<br class=""><br class="">then a hard failure stating "option-c format not found" (or something similar) would have been helpful.<br class=""></blockquote><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">In this case, even a "no .clang_format file found" message would've</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">been adequate, yes? Or did they have some other .clang_format file?</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Perhaps in verbose mode clang-format could print which .clang_format</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">file it used?</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div></blockquote><div><br class=""></div><div>I am not certain what his particular failure mode was, but providing an error message a la your proposal and/or a verbose mode that prints the path of the .clang-format file would be quite welcome and would meet the need.</div><div><br class=""></div><div>Kyle</div><br class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class="">Thanks,<br class="">Kyle<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Once we settle on a format, I expect the .clang-format to be included in the source-code repository, and this problem can be a non-issue. Until we get there, however, this would be a very helpful safety mechanism.<br class=""><br class="">That said, I'm very cognizant of the XY problem, and do not want to be a perpetrator of it.<br class=""><br class="">Thanks for your response,<br class="">Kyle<br class=""><br class=""><blockquote type="cite" class="">On Sep 15, 2020, at 3:14 AM, David Blaikie <<a href="mailto:dblaikie@gmail.com" class="">dblaikie@gmail.com</a>> wrote:<br class=""><br class="">"clang-format for each input file will try to find the .clang-format<br class="">file located in the closest parent directory of the input file." - so<br class="">it shouldn't matter which directory you invoke the command from. If<br class="">you have the .clang-format file in the parent of the file you want to<br class="">format, it should always get that format.<br class=""><br class="">Perhaps there's something broken in your setup that's causing that<br class="">behavior not to work?<br class=""><br class="">On Mon, Sep 14, 2020 at 5:47 PM Kyle Knoepfel via cfe-dev<br class=""><<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">Forgive me if this has already been discussed.<br class=""><br class="">I work on projects with different formatting guidelines. For simple cases, it is simple to embed the .clang-format file in the correct (parent) directory, run `clang-format -style=file ...` and everyone's happy. However, it is easy to get into a situation where the wrong format is applied, especially if you accidentally invoke the command from the wrong directory.<br class=""><br class="">Would Clang be opposed to a command line invocation such as:<br class=""><br class="">clang-format -style=custom:my-projects-format ...<br class=""><br class="">where a field in the .clang-format file would have the value 'my-projects-format', thus attributing the file to the format name? If a user specified something like -style=custom:my-unsupported-format, and such a format name could not be discovered in the .clang-format file, then it would be a hard failure, not letting a silent error slip by.<br class=""><br class="">Thanks for your input. If it is favorable, then I'm happy to explore implementing it.<br class=""><br class="">Kyle Knoepfel<br class=""><br class="">Software framework group leader, Fermilab<br class=""><br class="">_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</blockquote></blockquote></blockquote></blockquote></blockquote></div></blockquote></div><br class=""></body></html>