From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] presentation preparation
Date: Mon, 17 Feb 2003 10:00:42 -0500 [thread overview]
Message-ID: <c3453d8887ebd43d0907cbab81b163f0@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0302150923540.14996-100000@athena>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
Attached are some presentations I've done using
troff and page, along with tools that make them
easier.
You can play with the variables at the end of tmac.ppt
(or the definitions themselves) to add color to various
parts.
I tend to shy away from color usually, though.
The auth talk is black and white, while the oscpu
presentation adds grey.
Russ
[-- Attachment #2: doc.tar.gz --]
[-- Type: application/octet-stream, Size: 12370 bytes --]
next prev parent reply other threads:[~2003-02-17 15:00 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
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 [this message]
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=c3453d8887ebd43d0907cbab81b163f0@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).