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 15995 invoked from network); 14 Jan 2022 11:48:47 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 14 Jan 2022 11:48:47 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 9FB159D4D8; Fri, 14 Jan 2022 21:48:44 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 453799D4B3; Fri, 14 Jan 2022 21:48:19 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="EUWHOe4A"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 2D0379D4B2; Fri, 14 Jan 2022 21:48:16 +1000 (AEST) Received: from mail-pj1-f54.google.com (mail-pj1-f54.google.com [209.85.216.54]) by minnie.tuhs.org (Postfix) with ESMTPS id B20F29D06B for ; Fri, 14 Jan 2022 21:48:15 +1000 (AEST) Received: by mail-pj1-f54.google.com with SMTP id l16so3705011pjl.4 for ; Fri, 14 Jan 2022 03:48:15 -0800 (PST) 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=j8EIaB/GorpRluLptdeh+qFXov+1VrF1HLAtzeFZOeM=; b=EUWHOe4AaUYZZItfb1bC237eeGif9ZI3xEE/13veliDv1fnrvNclLlmgw2X7FeCwi0 7g0QkBavvzBC6NU5ndOSanBH3DkE06k2qPxp8+f+XZoXrqB7kyondFp+NJ0UPfpARP5W Lh446nI4PTXIS2dl/YOHh+2kle5X47tUwFGS0XKMsKFblieXXK2qVIjclto4Wsz8PcT7 7vj9hZtn41vP+K56v2/lqStmd57uQJ4wo8PXXiQaU9LBazXA5tBhgI5w3lPNTYjHfBB/ Bcvsvel6jZmces5fDFJt77kIuGpA0kyrk7g9+pud03sHA1kIgMmwYWXTnHGQ1BaNQe3G +ltA== 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=j8EIaB/GorpRluLptdeh+qFXov+1VrF1HLAtzeFZOeM=; b=QzGvwZQr1e0VLIJvQr3AH1bnlwXXydEecfLTKu1QOQbwRS4UtTdABDhPnsbTEHW0W0 bMDX7dLDN8r2YyRw26rE/WTyY7fELyT+o8gdF9PReZao+DYRTz3zEHjBrYagFspUSxgi s7PoxBM7RXHA9xo/VNn+1baMSPsmV44PDs5rTG9v4AMmJgLFp4IwdQwQHB52KrUPUbsg B3IjktsJDj/WWsHj7qRYitp2GaRyiz9puWwXSFtCNr6KLGtaL1KvrsMysfRWs0Wuq31b Qabw6endpxH/NvXjvUGfaTSgvP/Lrjoa2OTZvZyMatNIs4ndR4TK35ibI1xR4lmr4WlD 8qxw== X-Gm-Message-State: AOAM531omYmajEoi22l54YaMZKL+ODwfdCj/P+yTNJmlqFA4uq9PnKDM SJ50so5mhS9QZaDKlBMDkusH8kdeccy1j0mpZ3c= X-Google-Smtp-Source: ABdhPJxBBK/g268DrP/fwx9W/vfsgrZZbKJfZdFOQa0BdF7P3Y5/MLF69PVKj/OOf3IzYXpg39ljyT7wW++Uyx7VK9w= X-Received: by 2002:a17:90a:6043:: with SMTP id h3mr19612781pjm.140.1642160894880; Fri, 14 Jan 2022 03:48:14 -0800 (PST) MIME-Version: 1.0 References: <3BEC16DC-5F58-4D9E-8577-7578DE696F03@xs4all.nl> In-Reply-To: <3BEC16DC-5F58-4D9E-8577-7578DE696F03@xs4all.nl> From: Rob Pike Date: Fri, 14 Jan 2022 22:48:03 +1100 Message-ID: To: Jaap Akkerhuis Content-Type: multipart/alternative; boundary="000000000000cdadfa05d589600f" Subject: Re: [TUHS] Brian Kernighan and very early *roff history X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000cdadfa05d589600f Content-Type: text/plain; charset="UTF-8" It was definitely Dennis, at least for the cleanup part I was referring to. -rob On Fri, Jan 14, 2022 at 9:14 PM Jaap Akkerhuis wrote: > > > > On Jan 14, 2022, at 1:10, Rob Pike wrote: > > > > Dennis spent quite a bit of time cleaning up the troff code in the late > 1980s, if I remember right, moving it to modern C. He got annoyed by it one > day. > > If I remember correctly, it was actually Ken. He also turned it > in a single binary. (Troff -N turned it into nroff). > > > It was the "ditroff" variant although honestly I don't remember us ever > calling it that. It was just the current version of troff. Not sure where > the name came from. Perhaps it was us but I think of it as a foreign name. > > Originally Brian called it "Typesetter Independent Troff" in the > article he wrote about it and for some reason people started to > call it "Device Independent". > > jaap > > --000000000000cdadfa05d589600f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It was definitely Dennis, at least for the cleanup part I = was referring to.

-rob


On Fri, Jan 1= 4, 2022 at 9:14 PM Jaap Akkerhuis <j= aapna@xs4all.nl> wrote:


> On Jan 14, 2022, at 1:10, Rob Pike <robpike@gmail.com> wrote:
>
> Dennis spent quite a bit of time cleaning up the troff code in the lat= e 1980s, if I remember right, moving it to modern C. He got annoyed by it o= ne day.

If I remember correctly, it was actually Ken.=C2=A0 He also turned it
in a single binary.=C2=A0 (Troff -N turned it into nroff).

> It was the "ditroff" variant although honestly I don't r= emember us ever calling it that. It was just the current version of troff. = Not sure where the name came from. Perhaps it was us but I think of it as a= foreign name.

Originally Brian called it "Typesetter Independent Troff" in the<= br> article he wrote about it and for some reason people started to
call it "Device Independent".

=C2=A0 =C2=A0 =C2=A0 =C2=A0 jaap

--000000000000cdadfa05d589600f--