From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: walt@nea-fast.com, linux-kernel@vger.kernel.org
Subject: Re: printing from command line
Date: Fri, 22 Mar 2002 15:10:35 -0600 (CST) [thread overview]
Message-ID: <200203222110.PAA26889@tomcat.admin.navo.hpc.mil> (raw)
walt <walt@nea-fast.com>:
>This is a general linux question, not really a kernel question. Does
>anyone know if there is a "simple" good way to print code from linux at
>the command promt. On a Solaris machine,
>/usr/openwin/bin/mp -o -l filename
>gives me a page with 2 columuns, user_name, date, and pagenumber at the
>top of each column, and the filename at the bottom of each column. I've
>read lots of howtos and man pages, even wrote a perl script to wrap the
>lines for me, but I haven't figured out how to get the same format from
>Linux as I do from Solaris.
check the "pr" command:
pr -m file1 file2
Will format the output in two columns, file1 on the left, file2 on the right.
It doesn't include username, but does have the date (top left) and page number
(top right).
An arbitrary title/heading may be specified with the -h option. The
heading is at the top, center of each page.
I've found that a single column was best based on readability (most source
files will indent so far to the right that only a single column will do).
If you want fancier printing try enscript, this utility allows for 1/2/n
columns. (This one does a nice job for line numbers). The output is
postscript - so options for various fonts and sizes are available.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2002-03-22 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 21:10 Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-22 20:16 printing from command line walt
2002-03-22 21:20 ` Mr. James W. Laferriere
2002-03-22 21:26 ` Richard B. Johnson
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=200203222110.PAA26889@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=linux-kernel@vger.kernel.org \
--cc=walt@nea-fast.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.