From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] presentation preparation
Date: Sat, 15 Feb 2003 14:37:47 -0500 [thread overview]
Message-ID: <20030215193747.11670.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from Sam <sah@softcardsystems.com> of "Sat, 15 Feb 2003 09:30:49 EST." <Pine.LNX.4.30.0302150923540.14996-100000@athena>
| I could use the extant doc prep
| tools I'm becoming increasingly familiar
| with.
Not a Plan 9 specific answer, but... I rather like latex with the
prosper package. Ideally it is used to make pdf, and can take advantage
of acroread's features, but straight ps output should be usable.
next prev parent reply other threads:[~2003-02-15 19:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sah@softcardsystems.com>
2003-02-15 14:30 ` Sam
2003-02-15 19:37 ` Scott Schwartz [this message]
2003-02-15 19:48 ` andrey mirtchovski
2003-02-27 9:35 ` Ralph Corderoy
2003-02-28 18:44 ` [9fans] union directories Jack Johnson
2003-02-28 18:53 ` Russ Cox
2003-03-04 9:44 ` Adrian Tritschler
2003-02-15 20:49 ` [9fans] presentation preparation Richard Miller
2003-02-17 15:00 ` Russ Cox
2003-02-17 16:25 ` Fco.J.Ballesteros
2002-11-14 6:53 [9fans] how to avoid a memset() optimization Russ Cox
2002-11-14 10:22 ` Douglas A. Gwyn
2002-11-14 13:20 ` Sam
2002-11-14 15:20 ` Scott Schwartz
2002-11-14 15:26 ` Boyd Roberts
2002-11-14 15:34 ` plan9
2002-11-14 15:59 ` Sam
2002-11-14 18:57 ` Steve Kilbane
2002-11-15 10:51 ` Douglas A. Gwyn
2002-11-14 15:50 ` Dan Cross
2002-11-14 17:21 ` Douglas A. Gwyn
2002-11-14 18:51 ` Dan Cross
2002-11-14 15:50 ` Douglas A. Gwyn
2002-11-19 7:20 ` Roman V. Shaposhnick
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 15:53 [9fans] useful language extension, or no? rob pike, esq.
2002-07-16 15:05 ` Sam
2002-07-16 21:29 ` Steve Kilbane
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=20030215193747.11670.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--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).