From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] autoroff
Date: Thu, 8 Mar 2007 14:41:13 -0500 [thread overview]
Message-ID: <509071940703081141y48ed5b91nf5be66a65f2bdfad@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0703080849w55fd6df1k56403318fd814a33@mail.gmail.com>
very nice indeed.
most of my troff work these days is with man pages. it looks like
replacing the line:
{ 9 tbl $tmp.tr | 9 troff -ms | tr2post >$tmp.ps_
with
{ `{doctype $tmp.tr} | tr2post >$tmp.ps_
will get it to use the right macro packages (and other tools as
needed). i also added a ". 9.rc" up front to encourage it to pick up
plan9's troff and friends (since doctype provides command names
without paths).
both the original and my modified version seem to be getting fonts
wrong, with lots of overlap. likely a local issue.
next prev parent reply other threads:[~2007-03-08 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 16:49 Russ Cox
2007-03-08 19:41 ` Anthony Sorace [this message]
2007-03-08 20:00 ` Russ Cox
2007-03-08 20:31 ` Anthony Sorace
2007-03-08 21:15 ` Russ Cox
2007-03-11 6:58 ` Scott Schwartz
2007-03-11 8:08 ` Bakul Shah
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=509071940703081141y48ed5b91nf5be66a65f2bdfad@mail.gmail.com \
--to=anothy@gmail.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).