|
|
No reason to specify the path to the man page
To get nice postscript output from
man use the -t option. It is better to do it this way than piping through troff directly because there are lines in man files that specify to use other preprocessors such as tbl and eqn that you will not use unless you specify them in your pipeline as well. If you want a man page that turns-out not to be the first one and you use a Bourne-style shell, just do the appropriate MANPATH=... before your pipeline. Also, ps2pdf is not installed by default on MacOS X, but pstppdf appeared with 10.2 or so. So for example to get the man page as a pdf file for the man command itself, you could do:
Although there really is no reason for the pstopdf step as with 10.3 at least I can open postscript files in Preview.app.
I personally dislike the 'pretty-printing' of typeset man pages. I personally like to use something like this:
The col command strips away the escapes used for underlines and bold characters.
|
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.14 seconds |
|