From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id 6N9XHCKpemd/fQEAe85BDQ:P1 (envelope-from ) for ; Sun, 05 Jan 2025 15:45:38 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id 6N9XHCKpemd/fQEAe85BDQ (envelope-from ) for ; Sun, 05 Jan 2025 16:45:38 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=ljabl.com header.s=20220906 header.b=Ijq7eB0T; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=reject) header.from=ljabl.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1736091938; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=it+HALpd6l5YxAlngFjj0UvXsOn/hFY+axeNrtBRkZM=; b=ZHDxUx13gtkTeaDgaKGFq2qg+bM/l8CIY8tzE+GB1J+ifps/UMCtUQIEiHRCfXifLYZYhi bZaCx2FR4Q4Qbs1f9Z1kwCOcT+SSc04D9dYWHgiXdclipAL13vScTwRiwMZL4hWtheR6Ua X3ndYODWXLSRFxFewpy+DE5uNOoHISJ4by6v8ioiCHZBAe/SYrToa41WTUtfJi5yqA0zUM o0U63gbQAGanWAm6fVrUdpRNkU1Fy/EBksQldrWIdkwVJGgf417H7roGkWZKP9ELLWb87e EK8rg+Alvk5rsxzcRJK5uEYyBUoNdboI956fVkkrs+Dzrs5PziYJS7wJC0dvOg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=ljabl.com header.s=20220906 header.b=Ijq7eB0T; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=reject) header.from=ljabl.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1736091938; a=rsa-sha256; cv=none; b=bl9geSMIYSZLNArOyHdwMhWgzFscRzbzr+btgc9iV6MEkWAd6WEXnMNlqx1pOKytvuA5Y3 QeuYykaNRf2UCvRCx6wUe3YvICAefY6WLlj2u/XOdI2S2Dxu5k5Mz8LFltAItPw9/bH6Nm Fuog4aSC+x/Rnftcl53540t/T9aYmg2To/EBeUBggSVLqg11VzxUif2Qj05PFRtrLLgabl ijUga0tZF3WaF2nuZhY523zIWaaXD0smgKa4OQVYWinS+cAOT24biDSjSXHZ/n1FZiJ5mg HJaDox2DQNaW5RqogzilCvcfotLk0QYdBfyIs76NMy0KIRHkDyokFOPICmaeHg== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 535281A84D for ; Sun, 05 Jan 2025 16:45:38 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tUSo9-0006Gh-PT; Sun, 05 Jan 2025 10:44:53 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tUSUA-0002t4-Hz; Sun, 05 Jan 2025 10:24:14 -0500 Received: from mail.ljabl.com ([88.99.6.227]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tUSU8-00031a-Ak; Sun, 05 Jan 2025 10:24:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ljabl.com; s=20220906; t=1736090645; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=it+HALpd6l5YxAlngFjj0UvXsOn/hFY+axeNrtBRkZM=; b=Ijq7eB0T7WSOujlpe17Gw1neeSCAPJsZ+apDtF/lGfVlqTJmWJnRvMWwDzQ2/TwPBMwVer b2/3J/sua/zHRVr/OuKJdTx5/XMS06zcFtvjfVGHMVgzu+OyI9kbZTCSmGztESqsGywOMS mjHairhaYbOi6nRH7UcZ4I/Fr12XZvg= Received: by ljabl.com (OpenSMTPD) with ESMTPSA id 6d95a51c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sun, 5 Jan 2025 15:24:05 +0000 (UTC) Received: by fluorine (OpenSMTPD) with ESMTPA id 1366a013; Sun, 5 Jan 2025 16:24:04 +0100 (CET) Date: Sun, 5 Jan 2025 15:24:04 +0000 From: Lennart Jablonka To: onf , "G. Branden Robinson" , emacs-orgmode@gnu.org, groff@gnu.org Subject: Re: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)] Message-ID: Mail-Followup-To: onf , "G. Branden Robinson" , emacs-orgmode@gnu.org, groff@gnu.org References: <20250103083819.bvz53fcaluaxyubt@illithid> <20250104063731.cwp5fylyn5nj75lk@illithid> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Content-Language: en-US X-Clacks-Overhead: GNU Terry Pratchett Received-SPF: pass client-ip=88.99.6.227; envelope-from=vol@ljabl.com; helo=mail.ljabl.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sun, 05 Jan 2025 10:44:51 -0500 X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: 0.00 X-Spam-Score: 0.00 X-Migadu-Queue-Id: 535281A84D X-TUID: ZNnXZ/QP6AG+ [replying to two messages] Quoth onf: >On Sat Jan 4, 2025 at 7:37 AM CET, G. Branden Robinson wrote: >> At 2025-01-04T01:23:02+0100, onf wrote: >[…] >> > My impression of Plan 9's troff is that it's a poorly maintained >> > descendant of DWB troff that's used only to format manpages. It’s not only used to format man pages: It’s also used to format volume 2 of the manual; i.e., the papers in /sys/doc are formatted by troff. The papers at the state of the fourth edition’s abandonment (2015) is at https://9p.io/sys/doc/index.html ; see, for example, the https://9p.io/sys/doc/troff.pdf linked thence. Beside /sys/doc and /sys/man, the International Workshop on Plan 9¹ accepts papers written in -ms. And I know of at least one person who wrote some sort of thesis for a degree using troff on 9front. (Said thesis was on Plan 9.) Troff on 9front is not used very much to format man pages not written for Plan 9. It sometimes is, but not very often. There was no need to import -mdoc yet, for example. >> I wouldn't say _poorly_ maintained; its commit rate seems to match or >> even exceed its defect rate. This could illustrate (1) low adoption or >> (2) adequacy for the (limited?) purposes to which people apply it. [...] > >Which commit rate are you referring to? I thought the official sources >are at https://plan9.io/sources/plan9/sys/src/cmd/troff/ ... or maybe >you meant the 9front version? Yes, the sources there are the last sources of Plan 9 as distributed by Bell Labs. It was abandoned in 2015 and is now dead. Beside that, there is the commit rate of plan9port and that of 9front. I don’t care for plan9port. I do care about 9front. Per my understanding, troff on Plan 9 (and thus 9front and plan9port) is just bwk’s continuation of troff. The Unix system would have been replaced by Plan 9 with bwk continuing developing troff like nothing happened, only now on Plan 9 instead of on v10. Yes, there are few changes to troff on 9front. I remember fixing a little defect. If anything, it might get replaced by Neatroff at some point. Quoth G. Branden Robinson: >I'd like to see an attempt at reconstructing DWB 3.4 from the existing >DWB 3.3 code base (made portable) and an old snapshot of Plan 9, maybe >circa 2000. It'd be good to have a plausible exhibit of the end of the >line for AT&T Unix troff--what the body looked like at the murder scene. You can find old versions of Plan 9 at the website of the “Plan 9 Foundation”: https://p9f.org/dl/index.html . The troff sources are in /sys/src/cmd/troff. I doubt they changed very much in the last 30 years. >> > Poor, in general. Where Courier bold-italic existed, it was >> > sometimes called "CX". >> >> I meant support for CB and CI, not CBI. > >Also poor, outside of the horizon I previously articulated. :( > >System V Unix supported these names _only_ on the "aps" device >(Autologic APS-5). Plan 9 doesn't. DWB 3.3 doesn't. > >The "aps" device on Solaris 10 troff supports CB but not CI. Plan 9 does have those names. It has all of C, CO, and CW for Courier and CI, CB, and CX for Courier-{Oblique,Bold,BoldOblique}. ¹ The website is at https://iwp9.org/ , the last proceedings at https://10e.iwp9.org/10iwp9proceedings.pdf . The papers with the usual, traditional, ugly -ms extra half-inch at the right were set with troff.