From: Dan Cross <crossd@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Line Numbers Before SysIII nl? BSD num?
Date: Sat, 23 Jul 2022 07:01:33 -0400 [thread overview]
Message-ID: <CAEoi9W6nJiAigZj_OHB0nYmE7izsB1t5af5ZZKDVxGu1hjsDNA@mail.gmail.com> (raw)
In-Reply-To: <8NgHeeJiYEBE0zhtd9RdKIeYWcAwtxsnAj7YhVIvLpz-yt0__LeFvVzNNGgSNTeDGnVQy-qxkoHWvmRi84ybYyNAiMRDJuVoAaEG96UAu4s=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Sat, Jul 23, 2022, 3:56 AM segaloco via TUHS <tuhs@tuhs.org> wrote:
> [snip]
> So all in all, num was an attempt that petered out, but # stayed in ex.
> System III and 4.4BSD-Lite ed derivatives implement n, and nl was
> introduced in System III for the AT&T line and slowly cropped up
> elsewhere. System V picked up ex in 1982, allowing nl, ed with n, and ex
> with # in the AT&T line. GNU had one out of the gate when POSIX hit. BSDs
> were late to the party with regards to both ed with n as well as nl, with
> nl only being adopted after the last Berkeley releases and subsequent
> fracturing.
>
It may be worth noting that BSD had `cat -n` in 4BSD by October, 1980:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=4BSD/usr/man/man1/cat.1
That may explain the relatively late incorporation of `nl` in, at least,
the BSD lineage.
- Dan C.
[-- Attachment #2: Type: text/html, Size: 1546 bytes --]
next prev parent reply other threads:[~2022-07-23 11:03 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 [this message]
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
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=CAEoi9W6nJiAigZj_OHB0nYmE7izsB1t5af5ZZKDVxGu1hjsDNA@mail.gmail.com \
--to=crossd@gmail.com \
--cc=segaloco@protonmail.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).