From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Found and Purchased Unix 4.1 3B20S Manual
Date: Mon, 12 Dec 2022 07:38:21 -0600 [thread overview]
Message-ID: <20221212133821.nbrwjql5ebvoyr2l@illithid> (raw)
In-Reply-To: <Vyx45m543o8TrGgEvtJTxDN9aVQzRx54nV3uJlVfk2-NmzAo75u8MW-g3GpsmjImHskr02vtHohrmjO39HaDBGJ0X67tQo5sLYRu6oRGAwc=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
At 2022-12-12T06:15:22+0000, segaloco via TUHS wrote:
> NROFF and TROFF are on the same manual page in 4.1 but split to two
> separate ones in 5.0, perhaps indicating ditroff developments. I
> haven't looked at the differences in the actual pages yet.
If you have scans of these specific pages, I'd be curious to see them.
Thanks to my avocation, my brain's working set has a significant amount
of *roff history in it; maybe I can be useful here.[1] (The Unix 4.0
documentation with its January 1981 snapshot of newborn
device-independent troff was a fantastic find, in my opinion.)
I can guess what mptx is but I am curious about this "osd" macro
package. What was it for?
Regards,
Branden
[1] The pages might also help me identify and correct errors in groff
documentation.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-12 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 5:04 [TUHS] " segaloco via TUHS
2022-12-02 9:36 ` [TUHS] " Sergio Pedraja
2022-12-11 0:07 ` Jason T
2022-12-11 2:21 ` segaloco via TUHS
2022-12-11 6:28 ` John Cowan
2022-12-12 6:15 ` segaloco via TUHS
2022-12-12 13:38 ` G. Branden Robinson [this message]
2022-12-12 14:05 ` Ralph Corderoy
2022-12-12 14:25 ` G. Branden Robinson
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=20221212133821.nbrwjql5ebvoyr2l@illithid \
--to=g.branden.robinson@gmail.com \
--cc=segaloco@protonmail.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).