From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 5434 invoked from network); 24 May 2022 21:23:54 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 24 May 2022 21:23:54 -0000 Received: from mail-io1-f45.google.com ([209.85.166.45]) by 9front; Tue May 24 17:22:04 -0400 2022 Received: by mail-io1-f45.google.com with SMTP id s23so19588115iog.13 for <9front@9front.org>; Tue, 24 May 2022 14:22:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:subject:message-id:in-reply-to:references:organization :mime-version; bh=OxYaePtj+W/w9c7+o3+mYW5+wEcbCw/sd1Zxb0mg8C0=; b=KAw+pg5Qug+ow554ChEsygF74/aTHqwZV7dK2mgVLngrMOjQJj7O84LP36Ij4yBZ8a Ap/hOOePiMbDVhGIhqCvNokiJZUaEKrBisn11ssFiQRyen8nRBFO+iP2gtFJzrAcE86m H1hDwsayT3nc0/LXfeQPyd//MJJN99HfA+HkJU6aIxFiwzRJQlg6ZjW+sLiyT3Sr8mpr s6K/gDHfNFW7n6UScyjXeXTq5Umj/M9zTahRIQ7CPDuHatDLMz/b7eGtQhq6PTOz+MCP boHm7Kd7MJgQdDWacXp5SKIPno1x6nRp0JSVQOh/2tuA/yTZRb/gXXegOKfPCxe+6Qt1 B9Yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:organization:mime-version; bh=OxYaePtj+W/w9c7+o3+mYW5+wEcbCw/sd1Zxb0mg8C0=; b=lM43jY822wxtghlIBUOoG+koYszEqUbtUWiKOOl3rFZM/HkrIGK4k16kzJ2AKlNnol bXpJaEaOHaYfIhFKO66Vo7CAqIcoMS0Q3jE6BjgS327Ygz+SVWEm2IywH2DUgUfXFvLa Ogk5i4HJUtNaS/3pCYNGQZROQv7QDs0lg3rK6x/33wM/FQjI3z7FuRGwnSGpwUW18LmL TPpL3meoQI0oJtB9z3eHyjy4gGRdCsR3BVkbXduvt6IWPyQ98KWua2SvqogO41rYmthB KJohE0ytoG2Ie20Xsh/TMUAwokwifJpan6KvIrWMFavrNTQxKXZ2GOGw0ffkWcwpKZMf EUsg== X-Gm-Message-State: AOAM532Am6RWz8F/k+pQyPADDlTMr36NJ8RTvEUs1eWWLw3FL3UhiCjp 6oXgR+/XSB4td7GkLugUTU7VZzLJLQo= X-Google-Smtp-Source: ABdhPJyivGWywDJ+G6ZDrEJUBb+KGBhUAp5gmY5+FEB6t5mE0iC/mcTigL51FHUpWTAFXyT4oQ+OWA== X-Received: by 2002:a05:6638:3f13:b0:32e:8ccd:fbfa with SMTP id ck19-20020a0566383f1300b0032e8ccdfbfamr13791602jab.39.1653427319248; Tue, 24 May 2022 14:21:59 -0700 (PDT) Return-Path: Received: from spruce.localdomain ([2601:246:4e03:dc20::f726]) by smtp.gmail.com with ESMTPSA id w18-20020a92db52000000b002cf4ddfbd08sm4898847ilq.25.2022.05.24.14.21.58 for <9front@9front.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 May 2022 14:21:58 -0700 (PDT) Date: Tue, 24 May 2022 16:19:10 -0500 From: Amavect To: 9front@9front.org Message-ID: <20220524161910.777210fb@spruce.localdomain> In-Reply-To: References: <8A703EB8EACED4EFE003DD77486E70FE@eigenstate.org> <5BED10E2E8586FE65164516C75BFE8CC@eigenstate.org> <20220522221820.4294230d@spruce.localdomain> <20220523213811.003a6079@spruce.localdomain> Organization: Amavect Industries X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/LiuvG1V+pvGRPdLWcyk+6Lp" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: transactional secure SSL over AJAX deep-learning-oriented blockchain Subject: Re: [9front] patch: import replacement for ape/patch Reply-To: 9front@9front.org Precedence: bulk --MP_/LiuvG1V+pvGRPdLWcyk+6Lp Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 24 May 2022 16:39:28 +0000 Humm wrote: > Quoting RFC4263: Neat, but I have no clue how to configure process=3D in claws mail. Since application/x-troff-man is nonstandard, I'll just default it to text/troff and call it a day. > While much documentation for specific troffs indeed says that blank=20 > lines have the same effect as `.sp 1`=E2=80=94they do implement that, aft= er=20 > all=E2=80=94that behavior is not ubiquitous. A warning is given, for > example, by mandoc. Quoting mandoc(1): There's disagreement from others, but we can all agree that .PP is the correct choice for new paragraphs. It has slightly shorter spacing than a blank line in page. Attached is the final revision for ori's patch man page. Thanks, Amavect --MP_/LiuvG1V+pvGRPdLWcyk+6Lp Content-Type: multipart/mixed; boundary="upas-ulujlsfuxjngtbflvudfgieglp" Content-Disposition: inline This is a multi-part message in MIME format. --upas-ulujlsfuxjngtbflvudfgieglp Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit from postmaster@9front: The following attachment had content that we can't prove to be harmless. To avoid possible automatic execution, we changed the content headers. The original header was: Content-Type: text/troff Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=patch.man --upas-ulujlsfuxjngtbflvudfgieglp Content-Type: application/octet-stream Content-Disposition: attachment; filename="patch.man.suspect" .TH PATCH 1 .SH NAME patch \- apply diffs .SH SYNOPSIS .B patch [ .B -R ] [ .B -p .I nstrip ] [ .B -f .I maxfuzz ] [ .I patch ... ] .SH DESCRIPTION .I Patch takes a patch file in unified diff format and applies the differences to the file tree. If the file is not an exact match, it will search forwards and backwards for the surrounding context up to .I maxfuzz lines. .PP The following options are supported: .TP .B -R Reverse direction of the patch. Additions become removals, and the new and old file names are swapped. .TP .BI -p \ nstrip Remove the prefix containing .I nstrip leading slashes from each file path in the diff file. .TP .BI -f \ maxfuzz Controls how far .I patch searches for context when applying a patch. If not specified, this defaults to 250 lines. .SH SEE ALSO .IR diff (1), .IR git/export (1) .SH BUGS .PP The output of .B diff -c is not handled. .PP Reject files and backups are not supported. .PP All files are processed in memory, which limits the files handled to 2 gigabytes on 32-bit systems. --upas-ulujlsfuxjngtbflvudfgieglp-- --MP_/LiuvG1V+pvGRPdLWcyk+6Lp--