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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 1678 invoked from network); 24 May 2022 16:41:21 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 24 May 2022 16:41:21 -0000 Received: from mail-ed1-f45.google.com ([209.85.208.45]) by 9front; Tue May 24 12:39:36 -0400 2022 Received: by mail-ed1-f45.google.com with SMTP id p26so23794814eds.5 for <9front@9front.org>; Tue, 24 May 2022 09:39:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=kYFNQS8JnGZCxguGZIHku+bITg7Ng+I3j6k+EqBHxA0=; b=qOAEtEmWWMqieAp4NFxYvIZ703UpivfJpli+nmZ0q19BoYKTLfnQ/anoeU5P0v1TBk 1E0EiZGdMZPPuJHqeX8qwxKyS9NJ7pNCEnhkDXGSyZxuWXz7qRxeYS1EOTa8RIAYJtmq gBfWW+IYNA+C90MzZkphmubvShB1pcE/eFEA6Jlx0XPU1v8Xk1rkSo2AvrZLr61W9eBF VkvqSQ4JrLO8Mgqiu6fEM8SVo099Nzul6BUypqZ1k6fptXEyGhDY9AQUjNv1M1UnrD9J mH1pBm1jz3o0R+OpfJu9b3LosnVrDbFX7SPdDgfzkvobaur3t2DPayC2hyNxxuF7pdYO 3I4Q== 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:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to; bh=kYFNQS8JnGZCxguGZIHku+bITg7Ng+I3j6k+EqBHxA0=; b=rs0H5X1FP0RjmfLQ2pLQI2U2vZf+nSMOZDIQTXYjkEr3VqrTfMep1S0eayR1CYiKwi ecyRMwKeg0cM0pde674W27VHNr9gXVTqp3mAhPpsqids3Oqz31ZhGhWNj5CKsuL7RHtw 1w+z4XTQqwzpz6RDj3l6v5RRGTgPvDcpUpTZ25V6Ygt7zaCA3AaDQixmNTh/KZCbfxyl 04AdEXRXTpT7VSnvCJuM55MJ/jxHcaYBD0iWBDOXpVByTAnPRlydH1qU9bRio0U60wVF fpJathbwHyfs6r4Y0VzJG4qlEhBdIoeBdFUaKXVGQbAXY1ZMXB97Mae/Aiaziaqy84dN zPfQ== X-Gm-Message-State: AOAM530r5Xo4ICecVcfTK3sMgABQkBqqMleHwcQBymoArDmlQCOVzPG2 W3gnZ6jdS8lgNwrfp5MfKx0HFVpsKF8= X-Google-Smtp-Source: ABdhPJyk6rIuPKTjhEZugEJ+jAqn5YpOC7BCM/AJg/kJbO7yRi5sPUU+wvT0qjN58Q6sqdPg30D8Tg== X-Received: by 2002:a05:6402:1d4a:b0:42b:73bc:28d7 with SMTP id dz10-20020a0564021d4a00b0042b73bc28d7mr8866930edb.78.1653410371984; Tue, 24 May 2022 09:39:31 -0700 (PDT) Return-Path: Received: from beryllium.local (dyndsl-091-096-148-116.ewe-ip-backbone.de. [91.96.148.116]) by smtp.gmail.com with ESMTPSA id gz13-20020a170907a04d00b006fe9c65ffbcsm5803005ejc.155.2022.05.24.09.39.30 for <9front@9front.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 May 2022 09:39:31 -0700 (PDT) Received: from localhost (beryllium.local [local]) by beryllium.local (OpenSMTPD) with ESMTPA id da284ad7 for <9front@9front.org>; Tue, 24 May 2022 18:39:29 +0200 (CEST) Date: Tue, 24 May 2022 16:39:28 +0000 From: Humm To: 9front@9front.org Message-ID: Mail-Followup-To: 9front@9front.org References: <8A703EB8EACED4EFE003DD77486E70FE@eigenstate.org> <5BED10E2E8586FE65164516C75BFE8CC@eigenstate.org> <20220522221820.4294230d@spruce.localdomain> <20220523213811.003a6079@spruce.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220523213811.003a6079@spruce.localdomain> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: CSS component CMS backend Subject: Re: [9front] patch: import replacement for ape/patch Reply-To: 9front@9front.org Precedence: bulk Quoth Amavect: >On Mon, 23 May 2022 12:57:23 +0000 >Humm wrote: > >> >Content-Type: application/x-troff-man >> >> text/troff exists. > >A man page is a specific kind of troff file. Quoting RFC4263: >Optional parameters: >[…] > process: Human-readable additional information for formatting, > including environment variables, preprocessor arguments and > order, formatter arguments, and postprocessors. The parameter > value may need to be quoted or encoded as provided for by > [N4.RFC2045] as amended by [N5.RFC2231] and [N6.Errata]. > Generating implementations must not encode executable content > and other implementations must not attempt any execution or > other interpretation of the parameter value, as the parameter > value may be prose text. Implementations SHOULD present the > parameter (after reassembly of continuation parameters, etc.) > as information related to the media type, particularly if the > media content is not immediately available (e.g., as with > message/external-body composite media [N3.RFC2046]). As examples are provided: text/troff ; process="dformat | pic -n | troff -ms" and text/troff ; process="use pic -n then troff -ms" >(do mime types even matter?) Yes. Well-behaved MUAs decide what to do with stuff by looking at those. For troff: No. >> In troff, blank lines are UB. They should be removed or replaced by >> lines with just a period. >> > >Is that true? I'm having trouble finding a reference. While much documentation for specific troffs indeed says that blank lines have the same effect as `.sp 1`—they do implement that, after all—that behavior is not ubiquitous. A warning is given, for example, by mandoc. Quoting mandoc(1): >blank line in fill mode, using .sp > (mdoc) The meaning of blank input lines is only well-defined in > non-fill mode: In fill mode, line breaks of text input lines are not > supposed to be significant. However, for compatibility with groff, > blank lines in fill mode are formatted like sp requests. To request > a paragraph break, use Pp instead of a blank line. >https://www.gnu.org/software/groff/manual/html_node/Basics.html >Sometimes a new output line should be started even though the current >line is not yet full; for example, at the end of a paragraph. To do >this it is possible to cause a break, which starts a new output line. >Some requests cause a break automatically, as normally do blank input >lines and input lines beginning with a space. The groff docs are obnoxious in not telling you what is extension and what not or how portable something is. -- Humm