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 kOz2MdU0dGdJRgAAe85BDQ:P1 (envelope-from ) for ; Tue, 31 Dec 2024 18:15:50 +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 kOz2MdU0dGdJRgAAe85BDQ (envelope-from ) for ; Tue, 31 Dec 2024 19:15:49 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=UDQo9Qb0; 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=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1735668948; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=7pYMdCCDZSq0cs8SOZv/65PHlru1BibPwPtRChbcUSw=; b=gga6/40Q2AwftSaUCW7KTl9Zc8GRukTUaed5S3zKUalRZSiWizxvrAR91Fqe0ITDan4iRd F0ygwmK7ANuHDhzbPfAlZ6IgosHtTpWjO2HwjErHLzZqL8JNqtuShN3yAob3kiba8FLw4U jXZPdS9k07H2NCJfuJGfx0TdPxB9y5SDIT8277fq/F1ZHOaYCe0JKZm0cPwYcK+xAMvckW htas+4IsduzMGKkse+KEsKcGLBDYzilEacbo3VLKPMaUb/p8MOPLOa/JB0Zb6qpG+ZT5LC zBjrh2w/cDZ+s8JO0rpnD7g3bO5mMyEgcoJDyenCaDLeqfKQjE3el+3tJBCOOQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=UDQo9Qb0; 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=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1735668948; a=rsa-sha256; cv=none; b=Wu02Wcb1sG/ajH4YTSLu8p1JExJBSfUp6o8M9Kh2FpgzD/gIiOkNdVwVqUTlkN4MkEV8Yy tzwq/KwCh4UUkamGsWSDwX1mQXTWLMeuTzS3J9fYfuNErKznOqC49IWcUTO/baXgMVngHQ eZLgcBw69Fa4WzRdZM5lt6KywtJKbQ8E5Xg6jaX7dShnmbDde4LKpBhpNzSYTygyJcH0Oy l6s7lOle91JXyO6ZtDlFqu5EkzpybgVUm8KcCbw1VyjKadUvLQgDasP5g/T4VjbQw8o2x4 DpV4Ba/V31ixYPIDrS2EhL+ALAUcRqvlPFw30NaoH59viciakYYqvV8mhBHmGQ== 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 B0AFA63925 for ; Tue, 31 Dec 2024 19:15:48 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSglV-0002YT-Iq; Tue, 31 Dec 2024 13:14:49 -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 1tSglJ-0002Xt-CH for emacs-orgmode@gnu.org; Tue, 31 Dec 2024 13:14:38 -0500 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tSglF-00053T-Fz for emacs-orgmode@gnu.org; Tue, 31 Dec 2024 13:14:36 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 210D4240027 for ; Tue, 31 Dec 2024 19:14:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1735668867; bh=8+R6UhqWWJ78NkEhKDPtRRBPiLixY+j7fm8WeX/Wn5A=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=UDQo9Qb00igaGhM7DiIzVm4onceIZPXEZx43jaiH+6PFR/jcUGIZHlyAFr0yNjzEq V0Td12H5sAJbvRELdsqluVXBGMDdZy0yura5APpT938i6kmEYbTKzjNztM34VcPYYc L9YEB1hG5F+BnGI63c+oNiBmleZgxfhsOemkQr7tpQQl9qhikWsJxiZrKRePKZ3S3P 0pVRqgYYvpbQLEe1dm+msKX9Bj96RLLP0XJ6DbPyeON1B2HKDbKJIAlPLPohwl5j4t pteOJ+BH+txMfoQcjNOfxi/FzIQUgPhNe7jEdZoF3V/puF9fO8/rA73xPxS9lHncRI i1h5ncJnW7lzQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YN1MQ2jSfz9rxG; Tue, 31 Dec 2024 19:14:26 +0100 (CET) From: Ihor Radchenko To: "G. Branden Robinson" Cc: emacs-orgmode@gnu.org, groff@gnu.org, Ingo Schwarze Subject: Re: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)] In-Reply-To: <20241231170034.nzmponxxjppqrhf5@illithid> References: <20241218172040.tyytdhbyl7annyli@illithid> <87ttav7mii.fsf@localhost> <20241231170034.nzmponxxjppqrhf5@illithid> Date: Tue, 31 Dec 2024 18:15:57 +0000 Message-ID: <87bjwrhg6a.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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: -4.48 X-Spam-Score: -4.48 X-Migadu-Queue-Id: B0AFA63925 X-TUID: nE2E2QE25sok "G. Branden Robinson" writes: > I understand now. I've taken some time to learn a bit more about Org > mode, and also that org-man.el seems to be something close to the > bleeding edge; in a Debian unstable chroot it was not provided by the > version of GNU Emacs (29.4) nor the "elpa-org" package (9.7.16). You looked up wrong file. Not org-man.el, but ox-man.el. It is a part of Org mode since forever (introduced before Org 4.12a - the first tagged release in our git repo - Jan 31, 2008; 16 years ago). > So I'll make some recommendations unfortunately without the benefit of > having field-tested them. You can do the following to try exporting to man from Emacs 29.4: 1. emacs -Q 2. M-: (require 'ox-man) RET 3. Open a sample .org file 4. C-c C-e M m (4) will produce a man file named after the .org file, in the same directory. >> And this discussion was about using \fC to represent "code" (also, >> "fixed width" and tables). We use \fC historically, and it is not very >> clear what could be a replacement that does not break Man export >> compared to previously produced results. > > The answer depends on how portable you want your man(7) output to be. A > major reason is that font names are not portable across output > devices;... 1. We want to avoid breaking cases when \fC did work (it is a minimum) 2. Ideally, we want things to work in _more_ cases 3. Even more ideally, we want things to work in all the cases If (1) is not possible, compromises will have to be made. I hope that we do not have to make compromises. Also, what if we leave \fC and add \f[CR]/.EX on top? AFAIU, the worst case scenario for \fC is that it does nothing. By leaving it there, we thus retain old working exports working while also adding appropriate format when \f[CR] is supported. >> From my reading of man 7 man, .EX/.EE are more suitable for paragraph >> markup: > ... > Yes. `EX`/`EE` works only with "displays". May you elaborate about the meaning of "displays"? > But it is worth noting that `EX`/`EE` is _more_ portable than `\fC`. In non-inclusive manner though. (cases when \fC works are not a subset of cases where EX/EE works). Correct me if I am wrong. > (I would also delete that trailing "\n". Avoid blank lines in man(7) > input.[3]) Do I understand correctly that blank line is sometimes interpreted as vertical spacing and sometimes ignored? > (As another aside, the stroke color selection escape sequences `\m` are > (a) GNU troff extensions, albeit supported by the same formatters that > `\f[CR]` is, but (b) probably unnecessary because nothing else in this > entire file seems to use any other color for anything.) May black sometimes be different from the default color? > You can test a generated man(7) document by asking groff(1) and man(7) > to lint it. > > $ groff -ww -rCHECKSTYLE=3 -man my-org-doc.man Thanks! This might be a good thing to add to our tests. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at