From: Tom Lyon <pugs78@gmail.com>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX Roff Manual
Date: Wed, 17 Jul 2024 15:45:04 -0700 [thread overview]
Message-ID: <CANxB0bQxFNQhU4aGr1OyzgvxFhSiXtrc_DBiRRmmTMYJiwhECg@mail.gmail.com> (raw)
In-Reply-To: <CANxB0bTHdnFJAzsHsvMHHkvG0hwy5yhJGcYxCe_aOtROE4HcrQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]
I had meant to copy TUSH on this/
On Wed, Jul 17, 2024 at 2:41 PM Tom Lyon <pugs78@gmail.com> wrote:
> I got excited by your mention of a S/360 version, but Doug's link talks
> about the GECOS version (GE/Honeywell hardware).
>
> Princeton had a S/360 version at about that time, it was a re-write of a
> version for the IBM 7094 done by Kernighan after spending a summer at MIT
> with CTSS and RUNOFF. I'm very curious whether the Princeton S/360 version
> spread to other locations. Found this article in the Daily Princetonian
> about the joy and history of ROFF.
> https://photos.app.goo.gl/zMWV1GRLZdNBUuP36
>
> On Wed, Jul 17, 2024 at 1:51 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
>
>> Just sharing a copy of the Roff Manual that I had forgotten I scanned a
>> little while back:
>>
>> https://archive.org/details/roff_manual
>>
>> This appears to be the UNIX complement to the S/360 version of the paper
>> backed up by Doug here:
>> https://www.cs.dartmouth.edu/~doug/roff71/roff71.pdf
>>
>> From the best I could tell, this predates both 1973's V3 and the 1971
>> S/360 version of the paper, putting it somewhere prior to 1971. For
>> instance, it is missing the .ar, .hx, .ig, .ix, .ni, .nx, .ro, .ta, and .tc
>> requests found in V3. The .ar and .ro, and .ta requests pop up in the
>> S/360 paper, the rest are in the V3 manpage (prior manpages don't list the
>> request summary).
>>
>> If anyone has some authoritative date information I can update the
>> archive description accordingly.
>>
>> Finally, this very well could be missing the last page, the Page offset,
>> Merge patterns, and Envoi sections of Doug's paper are not reflected here,
>> although at the very least, the .mg request is not in this paper so the
>> Merge patterns section probably wasn't there anyway.
>>
>> - Matt G.
>>
>
[-- Attachment #2: Type: text/html, Size: 2696 bytes --]
next prev parent reply other threads:[~2024-07-17 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 20:51 [TUHS] " segaloco via TUHS
2024-07-17 21:01 ` [TUHS] " Larry McVoy
2024-07-17 21:45 ` segaloco via TUHS
2024-07-18 0:42 ` Jonathan Gray
2024-07-18 1:28 ` Tom Lyon
2024-07-18 1:58 ` John Levine
2024-07-18 2:22 ` Tom Lyon
2024-07-18 4:23 ` Jonathan Gray
2024-07-18 11:11 ` arnold
[not found] ` <CANxB0bTHdnFJAzsHsvMHHkvG0hwy5yhJGcYxCe_aOtROE4HcrQ@mail.gmail.com>
2024-07-17 22:45 ` Tom Lyon [this message]
2024-07-18 0:18 ` Clem Cole
2024-07-18 0:33 ` Tom Lyon
2024-07-18 1:21 ` [TUHS] Re: roff at Princeton, " John Levine
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=CANxB0bQxFNQhU4aGr1OyzgvxFhSiXtrc_DBiRRmmTMYJiwhECg@mail.gmail.com \
--to=pugs78@gmail.com \
--cc=tuhs@tuhs.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.
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).