From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] proof(1)
Date: Tue, 15 Sep 2015 16:40:27 +0100 [thread overview]
Message-ID: <1442331627.2847726.384314161.3B8472FE@webmail.messagingengine.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1509151500370.2819@localhost>
On Tue, Sep 15, 2015, at 02:01 PM, Julius Schmidt wrote:
> Why does this program still exist?
> It seems to be a poor man's version of page(1).
> Is it ever useful?
>
I assume proof was for previewing documents to be printed; the name being short for "proof-read".
As for present use, the only one I can think of is to do with my preference for man -P (render man page as postscript and show in page), together with the fact that postscript doesn't work in page on my x61, but proof's text quality is so poor I couldn't be bothered.
--
Wir mussen wissen, wir werden wissen.
prev parent reply other threads:[~2015-09-15 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 13:01 proof(1) Julius Schmidt
2015-09-15 15:40 ` Ethan Grammatikidis [this message]
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=1442331627.2847726.384314161.3B8472FE@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.org \
/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).