Re: patch(1) max line length

[Steffen Nurpmeso <steffen%sdaoden.eu@localhost>]

Steffen Nurpmeso wrote in
 <20240712172239.8n2tqdo2@steffen%sdaoden.eu>:
 |Robert Elz wrote in
 | <28937.1720777772%jacaranda.noi.kre.to@localhost>:
 ||    Date:        Fri, 12 Jul 2024 08:15:57 +0000
 ||    From:        Emmanuel Dreyfus <manu%netbsd.org@localhost>
 ||    Message-ID:  <ZpDmPYpd366xt+Dt%homeworld.netbsd.org@localhost>
 ||
 ||| I note the specification does not forbid the 
 ||| handling of lines longer than LINE_MAX characters.
 ||
 ||No, it certainly does not do that.
 ||
 ||However applications (at least if there's any attempt at portability
 ||at all) shouldn't assume that will work.
 |
 |It is your fault to think normal rules apply to JSON, for sure.
 |It is exceptional, see for example
 |
 |  $ wc -lwc /var/tmp/steffen/.cache/.mupdf.history
 |      1    22 23240 /var/tmp/steffen/.cache/.mupdf.history
 |
 |They all do not care no more.  (I remove this once in a while, it

It must be said though that the (i maintain) MUA blindlessly saves
any user input as a single line, no matter the size.  The history
file format does not support line continuation.  (But i hope this
really is exceptional for me.)

 |would be even worse otherwise.)
 |You are assumed to use json_pp or something, ah, i think "jq".
 ...

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)