From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 2871 invoked from network); 23 Jul 2022 11:03:32 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 23 Jul 2022 11:03:32 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 783B040146; Sat, 23 Jul 2022 21:02:56 +1000 (AEST) Received: from mail-oa1-f44.google.com (mail-oa1-f44.google.com [209.85.160.44]) by minnie.tuhs.org (Postfix) with ESMTPS id 403FE40144 for ; Sat, 23 Jul 2022 21:02:47 +1000 (AEST) Received: by mail-oa1-f44.google.com with SMTP id 586e51a60fabf-f2a4c51c45so9120381fac.9 for ; Sat, 23 Jul 2022 04:02:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=H2g2MkwoWZy6V7VkbjHm33zgBLTC1kSmbyZFlwwrAQc=; b=hryJqDqCix5Yt1XlRGHcCYa9SHWYNacNFkRsrA9WvnZKrzMzj2ViogrxgWcUk9spGr 3UkLP9bEIOnzQw2D/47ClXk32855FZeTjyYieVSnYt0ly6aoOJFwUQCd2Nj2FW66VS7y f5+5Z8xA7mhNn21XD6pLP7UGT8g81O8cJWvcKt90jfVY22mKfFd1icb/r3/P4EZ9Hess aLhCcL2vvYq2HMpSRBy8M47Zfe14NZ/FEwjCnVPMTyUPDKkEg6bhywHJWHzivFyq724a iv1PscKvrC4+mGw1ziiDZXQVOJ3LYueYlC36AAAEODpuxCpQQfM+vAqYTLAPf33LD810 jDiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=H2g2MkwoWZy6V7VkbjHm33zgBLTC1kSmbyZFlwwrAQc=; b=MX2WCa0Gq1TCClcjsnXkK960Z3GGsdrMkLBknBBKT3vmdzRASEJ614+VWbxiHXPgLM FCsNsUSnAo3XgV34jANwq8W3c1HY6pZ5H7l2b+ZwF4eYt7eif1yV4x8Rg0NAuQcEtZJp zGLyfGevVbcJDdiRvbkZ7gS+mwN/fFlPQjPbS0WPE+rNTdQgqkSXH7m4pkNTy8nSI+6u 8M0fSt36jo6d0FkPyC+iG+aR9u0yHmvsYDYGzvhaO5fEkEfEkVpb6NiVLdDyCihrOpb/ r/ulM6Ee5Le05vrlOL/XaxYWlEhPdHHzfrM3JMFwUoidf7nwXHlE++tk4l4BWwgFoxnU UkKQ== X-Gm-Message-State: AJIora/0aC/Riaw2v/q8uo+tZk/hplyCWy1SV+epojmyiyLqWYXq8q0v 0zT1NrGIJGzeTp7Yv8FaykQReX0i9aIBWeWfjOnqkNAm0DQ= X-Google-Smtp-Source: AGRyM1vy++pcJjOgcif/VrB9Jmi/zilrqSL10NIWOVnF8Bk3MIqEFIEneyZJXDOLu46spQpFP0pR/kPgEopaX8Crj+A= X-Received: by 2002:a05:6870:4625:b0:fe:4636:cf73 with SMTP id z37-20020a056870462500b000fe4636cf73mr1971959oao.278.1658574106137; Sat, 23 Jul 2022 04:01:46 -0700 (PDT) MIME-Version: 1.0 References: <1oF87S-4zW-00@marmaro.de> <8NgHeeJiYEBE0zhtd9RdKIeYWcAwtxsnAj7YhVIvLpz-yt0__LeFvVzNNGgSNTeDGnVQy-qxkoHWvmRi84ybYyNAiMRDJuVoAaEG96UAu4s=@protonmail.com> In-Reply-To: <8NgHeeJiYEBE0zhtd9RdKIeYWcAwtxsnAj7YhVIvLpz-yt0__LeFvVzNNGgSNTeDGnVQy-qxkoHWvmRi84ybYyNAiMRDJuVoAaEG96UAu4s=@protonmail.com> From: Dan Cross Date: Sat, 23 Jul 2022 07:01:33 -0400 Message-ID: To: segaloco Content-Type: multipart/alternative; boundary="0000000000006e1abe05e476e070" Message-ID-Hash: EL5GKUCOEML5466FPQNQGFTQZ3BBYP6V X-Message-ID-Hash: EL5GKUCOEML5466FPQNQGFTQZ3BBYP6V X-MailFrom: crossd@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tuhs.tuhs.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: The Eunuchs Hysterical Society X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Line Numbers Before SysIII nl? BSD num? List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000006e1abe05e476e070 Content-Type: text/plain; charset="UTF-8" On Sat, Jul 23, 2022, 3:56 AM segaloco via TUHS 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. --0000000000006e1abe05e476e070 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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.=C2= =A0 System III and 4.4BSD-Lite ed derivatives implement n, and nl was intro= duced in System III for the AT&T line and slowly cropped up elsewhere.= =C2=A0 System V picked up ex in 1982, allowing nl, ed with n, and ex with #= in the AT&T line.=C2=A0 GNU had one out of the gate when POSIX hit.=C2= =A0 BSDs were late to the party with regards to both ed with n as well as n= l, with nl only being adopted after the last Berkeley releases and subseque= nt fracturing.

It may be worth noting that BSD had `cat -n` in 4BSD by Octob= er, 1980: https://minnie.tuhs.org/cgi-bin/utree.pl?file=3D4BSD/usr= /man/man1/cat.1

That= may explain the relatively late incorporation of `nl` in, at least, the BS= D lineage.

=C2=A0 =C2=A0= =C2=A0 =C2=A0 - Dan C.

=
--0000000000006e1abe05e476e070--