9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] how to print a program
Date: Tue,  7 Sep 2010 23:05:54 +0200	[thread overview]
Message-ID: <AANLkTinuEhCFAYCe14GiifKc_EspLpeK4LVf5f9n9Sn8@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimkgjjknwiSG8Mzpskw6sRReH5hxuBjuXzd-K3v@mail.gmail.com>

also, a nice feature of 'fmt' is that long lines are broken AND
indented according to the start of the just-being-processed line; this
is welcome...
R

On 7 September 2010 23:00, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
> Hello,
>
> I want to 'print' the 'page' program, i.e. put /sys/src/cmd/page/* on paper.
> I want different files start on new pages, with the header of every
> page being the file name and the page.
> For this the command
> a=`{ls} pr $a | lp -dstdout > toprint.ps
> is almost ok.
> That 'almost' is in the fact that long lines get truncated, which is
> highly undesirable.
> fmt -j
> could help, but it also replaces spaces and tabs by a single space, again bad.
> (btw. why
> fmt <>afile
> doesn't work?)
>
> So how?
> Can anybody help? (I mean, is there a one-liner?)
> Thank you!
> Ruda
>



  reply	other threads:[~2010-09-07 21:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 21:00 Rudolf Sykora
2010-09-07 21:05 ` Rudolf Sykora [this message]
2010-09-07 21:06 ` John Floren
2010-09-07 21:37   ` Rudolf Sykora
2010-09-07 21:48     ` erik quanstrom
2010-09-08  6:25   ` Rudolf Sykora
2010-09-08  7:08     ` Lawrence E. Bakst
2010-09-08 17:59       ` erik quanstrom
2010-09-08 18:42       ` Akshat
2010-09-08 19:16         ` Charles Forsyth
2010-09-07 21:19 ` erik quanstrom
2010-09-08 11:45 ` roger peppe
2010-09-08 13:55   ` Federico G. Benavento

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=AANLkTinuEhCFAYCe14GiifKc_EspLpeK4LVf5f9n9Sn8@mail.gmail.com \
    --to=rudolf.sykora@gmail.com \
    --cc=9fans@9fans.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).