From: "Mark C. Otto" <Mark_Otto@FWS.Gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] off topic: troff book
Date: Mon, 8 Jan 2001 10:06:16 -0500 [thread overview]
Message-ID: <3A59D768.BBB388F5@FWS.Gov> (raw)
In-Reply-To: <E14FZYe-000717-00@minster.cs.york.ac.uk>
I grew up with TeX but would agree with Rob on its pluses and minuses over
troff. A package that seems to build on both troff and TeX is lout,
http://snark.ptc.spbu.ru/~uwe/lout/lout.html. The language looks a lot like
troff, lout produces postscript output, and is written in ANSI C. I know it
would have to have significant advantages over troff, but it might fit well with
plan9.
Mark
next prev parent reply other threads:[~2001-01-08 15:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 10:29 John A. Murdie
2001-01-08 15:06 ` Mark C. Otto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:17 John A. Murdie
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-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
2001-01-06 17:53 ` Boyd Roberts
2001-01-07 1:20 ` Steve Kilbane
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=3A59D768.BBB388F5@FWS.Gov \
--to=mark_otto@fws.gov \
--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).