From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil dies?
Date: Sun, 14 Oct 2007 12:54:12 -0400 [thread overview]
Message-ID: <5548a58945240b8bdb6d172f620aa3f8@plan9.bell-labs.com> (raw)
In-Reply-To: <140e7ec30710132139r13e5eba5w6ea91e8b5518e6cd@mail.gmail.com>
`man -P' running small machines out of memory is probably due to its
use of ghostscript, which seems to often use 10MB or more. I use
`man -p' instead.
next prev parent reply other threads:[~2007-10-14 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 9:58 Yaroslav
2007-10-12 14:10 ` erik quanstrom
2007-10-14 4:39 ` sqweek
2007-10-14 16:54 ` geoff [this message]
2007-10-15 7:59 ` Yaroslav
2007-10-15 12:50 ` erik quanstrom
2007-10-15 12:56 ` erik quanstrom
2007-10-23 9:47 Bituman
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=5548a58945240b8bdb6d172f620aa3f8@plan9.bell-labs.com \
--to=geoff@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).