Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Sep 2005 22:32:03 +0200
From:      Stijn Hoop <stijn@win.tue.nl>
To:        Giorgos Keramidas <keramida@ceid.upatras.gr>, Gerard Seibert <gerard-seibert@suscom.net>, freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: Printing MAN pages
Message-ID:  <20050908203203.GP20229@pcwin002.win.tue.nl>
In-Reply-To: <20050908175519.GA20222@falcon.midgard.homeip.net>
References:  <Pine.WNT.4.63.0509081012070.3172@Treneq.frvorepbz.arg> <43206857.1010803@daleco.biz> <20050908165328.GB37407@orion.daedalusnetworks.priv> <20050908173646.GO20229@pcwin002.win.tue.nl> <20050908175519.GA20222@falcon.midgard.homeip.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--r5lq+205vWdkqwtk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 08, 2005 at 07:55:19PM +0200, Erik Trulsson wrote:
> On Thu, Sep 08, 2005 at 07:36:46PM +0200, Stijn Hoop wrote:
> > On Thu, Sep 08, 2005 at 07:53:28PM +0300, Giorgos Keramidas wrote:
> > > Gerard Seibert wrote:
> > > > I am trying to figure out how to print 'man' pages. If I try a simp=
le
> > > > redirect, such as: "man foo > foo.txt" the new file is loaded with
> > > > control symbols, etc. that are not really printable. I want to save
> > > > the files if possible, and print them out at a later date. It that =
is
> > > > not possible, how would I go about printing them out in real time?
> > >=20
> > > 	man -t foo > foo.ps
> > >=20
> > > will generate Postscript output, which is a lot better for printing.
> >=20
> > Highly useful to know, but shouldn't we update the man page for man(1)?
> >=20
> >      -t          Use /usr/bin/groff -S -man to format the manual page, =
passing
> >                  the output to stdout.  The output from /usr/bin/groff =
-S -man
> >                  may need to be passed through some filter or another b=
efore
> >                  being printed.
> >=20
> > This does not exactly spell 'output postscript' to me...
>=20
> It does if you know that postscript is the default output format of
> groff.   If one doesn't know what format groff outputs by default, it is
> easily learned by reading the groff(1) manpage.

True. I'm all in favor of a little bit more userfriendliness in man pages
as long as it's not overkill though.

How about:

	-t	Generate a Postscript version of the manpage, intended for
		printing, by using /usr/bin/groff -S -man to format the manual
		page, passing the output to stdout.  The output from
		/usr/bin/groff -S -man may need to be passed through some
		filter or another before being printed.

That way I can do /print in less and still get some useful hint.

I'm no good with {t,g,n}roff and written English, so no patch...

--Stijn

--=20
"Harry, I'm going to let you in on a little secret. Every day, once a day,
 give yourself a present. Don't plan it, don't wait for it, just let it
 happen. Could be a new shirt at the men's store, a catnap in your office
  chair, or... two cups of good, hot, black coffee. Like this."
		-- Special Agent Dale Cooper, "Twin Peaks"

--r5lq+205vWdkqwtk
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFDIJ/DY3r/tLQmfWcRAjudAJ4x0q/dNreRtpllDASCgN8DetNtmgCffMQ8
01xLFi2Ph6wuCqS0luJa+lg=
=bzu8
-----END PGP SIGNATURE-----

--r5lq+205vWdkqwtk--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050908203203.GP20229>