emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lennart Jablonka <vol@ljabl.com>
To: onf <onf@disroot.org>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>,
	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/)]
Date: Sun, 5 Jan 2025 15:24:04 +0000	[thread overview]
Message-ID: <Z3qkFMU7x5XVphTM@fluorine> (raw)
In-Reply-To: <D6TK8RHW3IDG.13FFHOYKS92PM@disroot.org>

[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.


  reply	other threads:[~2025-01-05 15:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01  7:51 [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)] Xiyue Deng
2024-03-03 13:30 ` Ihor Radchenko
2024-03-12  0:06   ` Xiyue Deng
2024-03-13 11:25     ` Ihor Radchenko
2024-03-14 21:46       ` Jeremy Sowden
2024-05-22  9:54         ` Ihor Radchenko
2024-12-18 17:20         ` G. Branden Robinson
2024-12-22 15:41           ` Ihor Radchenko
2024-12-31 17:00             ` G. Branden Robinson
2024-12-31 18:15               ` Ihor Radchenko
2024-12-31 18:42                 ` onf
2024-12-31 18:54                   ` onf
2025-01-01  9:38                   ` Ihor Radchenko
2025-01-01 12:30                     ` onf
2025-01-02 14:29                       ` onf
2025-01-02 17:47                       ` [BUG] ox-man: Nested markup is broken (was: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]) Ihor Radchenko
2025-01-02 21:51                         ` onf
2025-01-03  8:38                           ` [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)] G. Branden Robinson
2025-01-04  0:23                             ` onf
2025-01-04  6:37                               ` G. Branden Robinson
2025-01-04 20:10                                 ` onf
2025-01-05 15:24                                   ` Lennart Jablonka [this message]
2025-01-04 13:26                             ` Ihor Radchenko
2025-01-04 16:22                               ` Dave Kemper
2025-01-04 17:37                                 ` Ihor Radchenko
2025-01-02 12:14                     ` G. Branden Robinson
2025-01-04 12:21                       ` Ihor Radchenko
2025-01-02 12:38                 ` G. Branden Robinson
2025-01-02 14:21                   ` onf
2025-01-04 12:36                   ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z3qkFMU7x5XVphTM@fluorine \
    --to=vol@ljabl.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --cc=onf@disroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).