Hi, On 23.04.2025 22:08, Nico Williams wrote:
On Wed, Apr 23, 2025 at 12:53:18PM -0700, Ted Lemon wrote:What we really want is to not gratuitously add newlines. That is, to not reflow the text. When a change is being made anyway, a newline in the middle of the change is fine. Lines should not be too long, because if they are then git diff output becomes incomprehensible. So ideally you want to flow things to a reasonable line width, but then not reflow to try to keep that length. You add newlines when adding text that makes lines too long, but never reflow.Yes. That exactly.
If you are using editorial tools, it makes the source code unreadable when it is not occasionally reflowed. Having a contextual diff would be far better. Yes, I want a pony, but at least I'm not asking for a unicorn.
Eliot
Of course, this is a hard discipline to follow.For me that means setting textwidth=0 when editing these things. And remembering not to reformat with `gqap` and similar. E.g., in this very email I used `gqj` to reflow the above quoted paragraph that would otherwise have been an annoyingly long line for me given that my terminal has 138 columns. Nico
OpenPGP_0x87B66B46D9D27A33.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ rfc-interest mailing list -- rfc-interest@rfc-editor.org To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
