From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] off topic: troff book
Date: Fri, 5 Jan 2001 19:29:59 +0000 [thread overview]
Message-ID: <200101051929.TAA04968@whitecrow.demon.co.uk> (raw)
In-Reply-To: Your message of "Sat, 06 Jan 2001 01:54:53 +1100." <000d01c07727$76985ae0$8692fea9@coma>
Boyd boyded thus:
> knuth had lost his mind [tex]. lamport was a screwhead [latex].
>
> gimme raw troff anyday...
Hold on. TeX and LaTeX have their good and bad points, but exactly
how did they screw up in ways that troff didn't? Off the top of my
head, the only thing that comes to mind is that troff would read
from stdin, while tex would insist on a named file, getting in the
way of pipelining. But that's more a style of use, rather than of
the systems themselves.
steve
next prev parent reply other threads:[~2001-01-05 19:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 19:26 James A. Robinson
2001-01-02 17:44 ` John E. Gwyn
2001-01-05 9:48 ` Allan J. Heim
2001-01-05 14:54 ` Boyd Roberts
2001-01-05 19:29 ` Steve Kilbane [this message]
2001-01-06 17:53 ` Boyd Roberts
2001-01-06 18:31 ` [9fans] " Jim Choate
2001-01-07 1:20 ` [9fans] " Steve Kilbane
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:17 John A. Murdie
2001-01-08 10:29 John A. Murdie
2001-01-08 15:06 ` Mark C. Otto
2001-01-07 15:17 rob pike
2001-01-08 9:54 ` Luis Fernandes
2001-01-08 16:18 ` Douglas A. Gwyn
2001-01-08 20:07 ` Dan Cross
2001-01-12 9:32 ` saroj
2001-01-12 17:17 ` Douglas A. Gwyn
2001-01-12 17:51 ` Boyd Roberts
2001-01-16 16:25 ` saroj
2001-01-12 18:20 ` William K. Josephson
2001-01-12 18:51 ` Boyd Roberts
2001-01-16 16:31 ` saroj
2001-01-08 17:19 ` James A. Robinson
2001-01-08 19:21 ` Howard Trickey
2001-01-09 9:38 ` Andy Newman
2001-01-09 9:54 ` Boyd Roberts
2001-01-10 0:16 ` Steve Kilbane
2001-01-11 9:50 ` Douglas A. Gwyn
2001-01-02 10:54 steve.simon
2001-01-03 8:29 ` Boyd Roberts
2001-01-05 9:49 ` [9fans] " John E. Gwyn
2001-01-05 14:52 ` Boyd Roberts
2000-08-19 21:44 Boyd Roberts
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=200101051929.TAA04968@whitecrow.demon.co.uk \
--to=steve@whitecrow.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).