From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Proliferation of options is great simplification of pipes, really?
Date: Wed, 24 Feb 2021 14:38:00 -0500 [thread overview]
Message-ID: <1614195484.3256.for-standards-violators@oclsc.org> (raw)
To fill out the historical record, the earliest doctype I know of
was a shell (not rc) script. From my basement heater that happens
to run 10/e:
b$ man doctype | uniq
DOCTYPE(1) DOCTYPE(1)
NAME
doctype - guess command line for formatting a document
SYNOPSIS
doctype [ option ... ] [ file ]
DESCRIPTION
Doctype guesses and prints on the standard output the com-
mand line for printing a document that uses troff(1),
related preprocessors like eqn(1), and the ms(6) and mm
macro packages.
Option -n invokes nroff instead of troff. Other options are
passed to troff.
EXAMPLES
eval `doctype chapter.?` | apsend
Typeset files named chapter.0, chapter.1, ...
SEE ALSO
troff(1), eqn(1), tbl(1), refer(1), prefer(1), pic(1),
ideal(1), grap(1), ped(9.1), mcs(6), ms(6), man(6)
BUGS
It's pretty dumb about guessing the proper macro package.
Page 1 Tenth Edition (printed 2/24/2021)
doctype(1) is in the 8/e manual, so it existed in early 1985;
I bet it's actually older than that. The manual page is on
the V8 tape, but, oddly, not the program; neither is it in
the V10 pseudo-tape I cobbled together for Warren long ago.
I'm not sure why not.
The version in rc is, of course, a B-movie remake of the
original.
Norman Wilson
Toronto ON
next reply other threads:[~2021-02-24 19:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 19:38 Norman Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-23 15:04 Steve Simon
2021-02-24 2:42 ` M Douglas McIlroy
2021-02-23 2:47 M Douglas McIlroy
2021-02-23 10:42 ` Jaap Akkerhuis
2021-02-23 13:23 ` Brantley Coile
2021-02-23 13:49 ` Ralph Corderoy
2021-02-22 2:34 Will Senn
2021-02-22 3:32 ` G. Branden Robinson
2021-02-22 4:32 ` Dan Stromberg
2021-02-22 4:34 ` Will Senn
2021-02-22 5:45 ` G. Branden Robinson
2021-02-22 15:49 ` John P. Linderman
2021-02-22 15:57 ` William Cheswick
2021-02-22 16:03 ` John P. Linderman
2021-02-22 21:16 ` G. Branden Robinson
2021-02-22 16:02 ` Warner Losh
2021-02-22 16:12 ` Robert Clausecker
2021-02-22 17:15 ` John Cowan
2021-02-23 0:24 ` Steffen Nurpmeso
2021-02-22 21:14 ` G. Branden Robinson
2021-02-22 7:20 ` Rich Morin
2021-02-22 18:27 ` Jon Steinhart
2021-02-22 19:30 ` Richard Salz
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=1614195484.3256.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
--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).