From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu, ancipites@earthlink.net
Subject: Re: [9fans] problems
Date: Tue, 1 Aug 2000 15:09:19 -0400 [thread overview]
Message-ID: <200008011909.PAA15275@smtp3.fas.harvard.edu> (raw)
1. My printer's paper tray doesn't hold enough sheets to
print the manuals. It looks as though, in devlpt.c, that
outch() doesn't check for Fpe when it finds an error. This
was encountered when trying to print vol1.ps.
That has always annoyed me. If you
tell me what the code should be I'll fix it.
Russ
next reply other threads:[~2000-08-01 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 19:09 Russ Cox [this message]
2000-08-01 20:10 ` [9fans] nvram etc Boyd Roberts
2000-08-01 20:42 ` [9fans] problems D. Brownlee
2000-08-01 21:04 ` D. Brownlee
-- strict thread matches above, loose matches on Subject: below --
2000-08-01 21:26 Russ Cox
2000-08-01 22:48 ` D. Brownlee
2000-07-30 15:20 [9fans] drawterm etc Russ Cox
2000-07-31 9:09 ` [9fans] problems D. Brownlee
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=200008011909.PAA15275@smtp3.fas.harvard.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=ancipites@earthlink.net \
/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).