Re: .clang-format: how useful, how often used, and how well maintained?

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 23, 2025, 16:26 UTC
Message-ID: <xmqq34bq77b8.fsf@gitster.g>
In-Reply-To: <CAOLa=ZSuEAwj==9+B-nYikyQtOxREf8ZEfJ9L_YxU8yU0ro-zA@mail.gmail.com>

Karthik Nayak <karthik.188@gmail.com> writes:

Show 12 quoted lines

>> For that, there are a few things we'd probably need to do:
>>
>>  - Improve our tooling so that the develper can check a range of
>>    commits they made before running format-patch, and other
>>    situations.
>>
>>  - Improve .clang-format rules to reduce false positives.
>>
>
> I think the biggest issue for this is around line wrapping, I'm
> considering just removing it from the '.clang-format'. Perhaps we could
> add it to our '.editorconfig'?

I would not stop others from trying to improve the rules in such a way that only an overly long lines (like >120 columns) are folded to reasonable length (line ~72 columns) without doing anything else (like not concatenating adjacent lines only because the result would be shorter than 80 columns), but if it is more involved than we can manage, removing it from .clang-format so that "make style" would not use would be the best (or "the least bad") approach.