From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] *roff history as told to GNU
Date: Wed, 12 Jan 2022 15:48:45 -0500 (EST) [thread overview]
Message-ID: <20220112204845.C365618C08A@mercury.lcs.mit.edu> (raw)
> From: Dan Cross
> a port of the _CTSS_ BCPL ROFF sources purportedly written by Doug. I
> wonder if that was actually a thing, or an error?
> ...
> Fortunately, the source [of the original CTSS runoff] is online:
> ...
> Indeed; one finds the following in at least one of the Multics RUNOFF
> source files:
It sounds like all the steps in the chain have pretty definitive evidence -
_except_ whether there was ever a CTSS RUNOFF in BCPL, from Doug.
Happily, we have someone here who should be able to answer that! :-)
Noel
next reply other threads:[~2022-01-12 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 20:48 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-01 3:15 [TUHS] TeX and groff (was: roff(7)) Larry McVoy
2022-01-10 19:00 ` Blake McBride
2022-01-11 1:59 ` [TUHS] Demise of " Greg 'groggy' Lehey
2022-01-11 2:13 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-11 2:42 ` Larry McVoy
2022-01-11 15:47 ` Clem Cole
2022-01-11 19:20 ` John Cowan
2022-01-11 20:06 ` Clem Cole
2022-01-12 8:54 ` arnold
2022-01-12 16:33 ` Dan Cross
2022-01-12 18:06 ` [TUHS] *roff history as told to GNU G. Branden Robinson
2022-01-12 18:34 ` Dan Halbert
2022-01-12 22:48 ` Clem Cole
2022-01-12 23:27 ` Charles H. Sauer
2022-01-13 0:35 ` Adam Thornton
2022-01-12 20:01 ` Dan Cross
2022-01-12 22:32 ` Clem Cole
2022-01-13 2:38 ` John Labovitz
2022-01-13 7:42 ` Lars Brinkhoff
2022-01-13 13:47 ` John Labovitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220112204845.C365618C08A@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
--subject='Re: [TUHS] *roff history as told to GNU' \
/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
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 NNTP newsgroup(s).