From: Larry McVoy <lm@mcvoy.com>
To: Jaap Akkerhuis <jaapna@xs4all.nl>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Brian Kernighan and very early *roff history
Date: Fri, 14 Jan 2022 06:08:55 -0800 [thread overview]
Message-ID: <20220114140855.GB11735@mcvoy.com> (raw)
In-Reply-To: <3BEC16DC-5F58-4D9E-8577-7578DE696F03@xs4all.nl>
On Fri, Jan 14, 2022 at 11:13:35AM +0100, Jaap Akkerhuis wrote:
>
>
> > On Jan 14, 2022, at 1:10, Rob Pike <robpike@gmail.com> wrote:
> >
> > Dennis spent quite a bit of time cleaning up the troff code in the late 1980s, if I remember right, moving it to modern C. He got annoyed by it one day.
>
> If I remember correctly, it was actually Ken. He also turned it
> in a single binary. (Troff -N turned it into nroff).
>
> > It was the "ditroff" variant although honestly I don't remember us ever calling it that. It was just the current version of troff. Not sure where the name came from. Perhaps it was us but I think of it as a foreign name.
>
> Originally Brian called it "Typesetter Independent Troff" in the
> article he wrote about it and for some reason people started to
> call it "Device Independent".
TIT vs DIT might be why?
next prev parent reply other threads:[~2022-01-14 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 0:04 Tom Lyon via TUHS
2022-01-14 0:10 ` Rob Pike
2022-01-14 7:38 ` arnold
2022-01-14 10:13 ` Jaap Akkerhuis
2022-01-14 11:48 ` Rob Pike
2022-01-14 14:08 ` Larry McVoy [this message]
2022-01-14 11:59 ` Angelo Papenhoff
2022-01-14 13:07 Noel Chiappa
2022-01-14 13:27 ` Angelo Papenhoff
2022-01-14 13:35 ` Ralph Corderoy
2022-01-14 13:55 ` Will Senn
2022-01-14 13:58 ` Will Senn
2022-01-14 14:25 ` Will Senn
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=20220114140855.GB11735@mcvoy.com \
--to=lm@mcvoy.com \
--cc=jaapna@xs4all.nl \
--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).