The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Rob Pike <robpike@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Line Numbers Before SysIII nl? BSD num?
Date: Sun, 24 Jul 2022 13:45:52 -0600	[thread overview]
Message-ID: <CANCZdfpR40ycYvra+_soK_XUvTFzf6Ji9b2RJ6FzkJHyxLXdmQ@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgwTgbHG0Ux6oO=rKp9Rh0yx0Fo2UL=g7V8G=uw2zLLK0A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]

By 1984 (so some years after the formative stage in the era between 4.2BSD
and 4.3BSD), there
were a number of different programs on the net (USENET's source groups) to
pretty print things
on laser or line printers: grind, tgrind, vgrind, ete. These all had a
dozen different ways to gaudy up
the output (err, present the listing in a more aesthetically pleasing way):
Line numbers, line numbers
every 5 or 10 lines, line spacing tweaks, keywords as bold or italics,
frames around the output,
"two up" printing, various special behavior for functions (grey bands for
start of functions, function
definitions in bold, etc), as well as specialized options for assembler /
object renderings, etc. Most
were targeted at laser printers, but some were a better version of pr/lpr
for line printer output. Some
targeted postscript directly, while others used TeX, troff, etc in a
pipeline to gain some device
independence. Oh what a long way from pr -n these were. But at the time it
really helped me to
understand the power of the unix philosophy because these 'all in'
approaches were great until
you wanted to get a few steps beyond the beaten path and then it became
impossible (given the
great number of combinatorics for these options, many of the programs
produced odd results for
some combinations of options).

For day to day stuff, I hated these and used simpler options. But for
producing nice looking listings
for appendixes for papers / reports / assignments I'd written for school
they weren't half bad if
you avoided the worst of the gaudiness options. :)

Warner


On Sat, Jul 23, 2022 at 7:21 AM Rob Pike <robpike@gmail.com> wrote:

> Very odd. I thought so too, but the 8th Edition manual says pr -n
> prints in n columns, while the 9th and 10th say it numbers the lines.
>
> No memory, if I ever knew, of what triggered that change.
>
> -rob
>
> On Sat, Jul 23, 2022 at 10:50 PM Norman Wilson <norman@oclsc.org> wrote:
> >
> > I had a vague memory that pr could be made
> > to number lines, but a quick check of the 7/e
> > manual says no.
> >
> > I expect Dan's right, and none of the 127 folks
> > felt much need to number lines on printouts
> > so nobody wrote the obvious simple tool.
> >
> > Ironic, since the Unix PDP-11 used by the patent
> > licensing office (and I think shared with the
> > research group, and that was how their first
> > PDP-11 was justified and funded) happened
> > because the patent folks needed line-numbered
> > output and roff was easily modified to do that.
> >
> > Maybe Doug or Ken or Steve has first-hand
> > memories.
> >
> > Norman Wilson
> > Toronto ON
> > (on a train shuffling toward Buffalo)
>

[-- Attachment #2: Type: text/html, Size: 3399 bytes --]

  parent reply	other threads:[~2022-07-24 19:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23  2:57 [TUHS] " segaloco via TUHS
2022-07-23  5:56 ` [TUHS] " markus schnalke
2022-07-23  7:55   ` segaloco via TUHS
2022-07-23 11:01     ` Dan Cross
2022-07-23 11:20       ` John Cowan
2022-07-23 12:00         ` Dan Cross
2022-07-23 12:49           ` Norman Wilson
2022-07-23 13:20             ` Rob Pike
2022-07-23 13:36               ` Ralph Corderoy
2022-07-23 14:33               ` John Cowan
2022-07-24 19:45               ` Warner Losh [this message]
2022-07-24 20:33                 ` segaloco via TUHS
2022-07-24 21:04                   ` Warner Losh
2022-07-23 17:35             ` Clem Cole
2022-07-23 18:40               ` Phil Budne
2022-07-23 18:51                 ` Nelson H. F. Beebe
2022-07-23 19:07                   ` Douglas McIlroy
2022-07-24 19:02           ` Tomasz Rola
2022-07-28  0:30             ` Tomasz Rola
2022-07-28  1:03               ` Phil Budne
2022-07-28  4:13                 ` [TUHS] SNOBOL and RATSNO William H. Mitchell
2022-07-29  4:28                   ` [TUHS] " Dave Horsfall
2022-07-29  5:07                   ` Tomasz Rola
2022-08-09  5:12                     ` Jonathan Gevaryahu
2022-08-09  6:11                       ` Rob Pike
2022-08-09 13:34                         ` Clem Cole
2022-08-09 15:15                           ` Andrew Hume
2022-08-09 18:26                             ` Clem Cole
2022-08-09 18:52                             ` Tom Teixeira
2022-08-09 21:25                             ` Rob Pike
2022-08-09 15:39                           ` Richard Salz
2022-08-09 13:56                         ` Larry McVoy
2022-08-09 16:45                         ` William H. Mitchell
2022-07-29  0:22                 ` [TUHS] SNOBOL and progeny [Was: Re: Re: Line Numbers Before SysIII nl? BSD num?] Stuff Received
2022-07-29  5:01                   ` [TUHS] " Charles H. Sauer
2022-07-29 14:07                     ` John Cowan
2022-07-29 15:37                   ` Dave Plonka

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=CANCZdfpR40ycYvra+_soK_XUvTFzf6Ji9b2RJ6FzkJHyxLXdmQ@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=robpike@gmail.com \
    --cc=tuhs@tuhs.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).