From: mutiny.mutiny@rediffmail.com (Mutiny )
Subject: [TUHS] TROFF made trivial
Date: 21 Nov 2017 18:43:33 -0000 [thread overview]
Message-ID: <1511268923.S.4264.20545.f4-234-160.1511289813.7546@webmail.rediffmail.com> (raw)
In-Reply-To: <201711211254.vALCsKKY007445@freefriends.org>
>I he finds one, I'll pass it on.great. Thanks a lot in advance.From: arnold at skeeve.comSent: Tue, 21 Nov 2017 18:25:23To: will.senn at gmail.com, leah at vuxu.orgCc: tuhs at minnie.tuhs.orgSubject: Re: [TUHS] TROFF made trivialLeah Neukirchen <leah at vuxu.org> asked:> >> I found this paper by bwk referenced in the Unix manpages,> >> in v4 as: TROFF Made Trivial (unpublished),> >> in v5 as: TROFF Made Trivial (internal memorandom),> >> also in the v6 "Unix Reading List",> >> but not anymore in v7.> >>> >> Anyone have a copy or a scan?Warner (I think):> > Is it what became known as "A TROFF Tutorial" in Volume 2 of the v7> > manual and was available as early as October 11, 1976 as referenced by> > Ossana in NROFF⁄TROFF User’s Manual as:> >> > 1.> >> > [5] B. W. Kernighan, A TROFF Tutorial, Bell Laboratories internal> > memorandumI asked Brian off-list. His answer:> Date: Tue, 21 Nov 2017 06:24:22 -0500 (EST)> From: Brian Kernighan <bwk at CS.Princeton.EDU>> To: arnold at skeeve.com> Subject: Re: "TROFF made trivial"?>> That's almost surely what became the Troff tutorial. I will poke> around to see if I have a paper copy.I he finds one, I'll pass it on.Arnold
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171121/07acf816/attachment.html>
prev parent reply other threads:[~2017-11-21 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 21:55 Leah Neukirchen
2017-11-20 22:00 ` Warner Losh
2017-11-20 22:41 ` Will Senn
2017-11-21 9:15 ` Leah Neukirchen
2017-11-21 12:54 ` arnold
2017-11-21 18:43 ` Mutiny [this message]
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=1511268923.S.4264.20545.f4-234-160.1511289813.7546@webmail.rediffmail.com \
--to=mutiny.mutiny@rediffmail.com \
/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).