From: Warner Losh <imp@bsdimp.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: Sun, 24 Jul 2022 15:04:05 -0600 [thread overview]
Message-ID: <CANCZdfq4xnhLdKWJ6=azV2R9JJn4nnfF1+FzozO9NMzNZiLseA@mail.gmail.com> (raw)
In-Reply-To: <erU-jvZgAtN30qQ5vCcvQWK_gjxAP7l25a59hXU-PBJsBcRtkSNoWCpN5OhX3MkvtU4QKfNffYSSv0_e3yU2d0JXCoX18mC82F4fMqWm2oM=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Sun, Jul 24, 2022 at 2:33 PM segaloco <segaloco@protonmail.com> wrote:
> All this discussion is making me incredibly glad I posed the question, as
> it does indeed seem that before num and nl, line numbering was more of a
> "to each their own" rather than there being a canonical best practice.
>
> By the way, what inspired the whole quandary in the first place was doing
> some editing on a V6 UNIX system and realizing I hadn't the foggiest idea
> of how to get the system to spit back line numbers to remind myself what
> addresses to supply to various ed commands. I suppose at the time using a
> context search was such an effective means of getting ed's cursor where you
> wanted it that having a means to number lines wasn't crucial to effectively
> working in ed, so long as one was good with their regex and searching.
>
> I'm realizing I might need to reach out to the maintainer of the nl
> manpage in FreeBSD (and perhaps other OSs and distros) as the history
> section of the page posits that nl was first introduced in SVR2, when in
> reality the earliest public offering was System III, although the trail
> goes cold at that point, I can only assume it came from USG.
>
I can update it. Done.
https://cgit.freebsd.org/src/commit/?id=8a02ea1dbc139862456f488464072719341658d7
Warner
[-- Attachment #2: Type: text/html, Size: 1775 bytes --]
next prev parent reply other threads:[~2022-07-24 21:05 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
2022-07-24 20:33 ` segaloco via TUHS
2022-07-24 21:04 ` Warner Losh [this message]
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='CANCZdfq4xnhLdKWJ6=azV2R9JJn4nnfF1+FzozO9NMzNZiLseA@mail.gmail.com' \
--to=imp@bsdimp.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).