Re: patch(1) max line length
Steffen Nurpmeso <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.userlevel |
|---|---|
| Message-ID | <20240712172239.8n2tqdo2@steffen%sdaoden.eu> |
Robert Elz wrote in <[email protected]>: | Date: Fri, 12 Jul 2024 08:15:57 +0000 | From: Emmanuel Dreyfus <[email protected]> | Message-ID: <[email protected]> | || 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 would be even worse otherwise.) You are assumed to use json_pp or something, ah, i think "jq". Btw my MUA calls its on-program-exit also very late, even documented so ("after terminal is torn down" or so). I find it much more natural to configure history during startup, when case $- finds *i*|*m*. --End of <[email protected]> --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)