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_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 9662 invoked from network); 4 Aug 2023 00:32:49 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 4 Aug 2023 00:32:49 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 90ADC42215; Fri, 4 Aug 2023 10:32:45 +1000 (AEST) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) by minnie.tuhs.org (Postfix) with ESMTPS id 043F5421D7 for ; Fri, 4 Aug 2023 10:32:40 +1000 (AEST) Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-51e28cac164so5647246a12.1 for ; Thu, 03 Aug 2023 17:32:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1691109158; x=1691713958; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3nO1ZjWV7Y8rIwLdlTr04/DOIo2GLKNeAn+qOKJCFIM=; b=OS++ED6W9DQMgOpxK8oUM1KVoOQLk7UHTb5/IsWwpKVggZwlrSe0LXc8AF/XH9svcs XIw2Bl3qbG+PZgwrwtA74cslbX716fkwcdfDWXrQ0Rpcm4jLHn/ZX6gY6AA9VvxW5pw1 Ztm3z9+J1KRAa5NK1TUX6sA82Qrbv0iX/MzEsGlgj+7ShJIWLZ6TcSRVl3Bwd7pllQQ0 9iENNezkpd2E4ykIFc+4Gz16W2IJICfiaGzwOmLQtFaVql582cWyhwGfIb2pnHIfMfbx gMCC13yRKEX5lIpklG0AgYrShSXdGhEhvsOI4ZZ0LX6L4/xKSLYUPHL45Ocj1QDHnqrj itGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691109158; x=1691713958; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3nO1ZjWV7Y8rIwLdlTr04/DOIo2GLKNeAn+qOKJCFIM=; b=K/usFWM0j4a249hrkgnbscKdPdX2XMknW6L96YFl1pXLjD21BpcdwV05sRfGYoTIHM eioPiXFf3R53nDZGpMD+jYrA2IVnnFb9iiDmBuCEkwMYDj3lrwLUKnrXlqWOTTonrdUm 2sxNLNAnYdURO13HL0QGzVwHA+mhfjrPqAx15HmjR3AutFZH81iPITDX1zOV7WTK3Xrf T0H3CXvWnxNIYzQCy2wAhSGhp66Wa886KVBq/ioeUMYNR4TK11+dgPgOWTQn3HXeTPde lYEAYkhnAk68atBFPf4vEQ5sj7BXmVGOsiEzM6984EdSR6jz6q/9Cp3I4/bSDFzMD0Ws 2Gfg== X-Gm-Message-State: AOJu0YwdjBtNlx5lLwQ9amILZ2HJ7BuiIztzus9TDZJCgR7vao4AbLs9 qfcHR46QfDeom8+J2n5JAcDIHo/mV0CMeRYFmTyDMA== X-Google-Smtp-Source: AGHT+IG4zP2Iad9x79UzWaNNSpqXbWm0EmlmEfe8crUQZ39olcdsxm2rX9GGT061UGz8B68wD6ffM7/ZxvLQnqSGnz8= X-Received: by 2002:a05:6402:26c4:b0:523:108c:9da1 with SMTP id x4-20020a05640226c400b00523108c9da1mr309870edd.15.1691109158258; Thu, 03 Aug 2023 17:32:38 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Thu, 3 Aug 2023 18:32:26 -0600 Message-ID: To: Adam Thornton Content-Type: multipart/alternative; boundary="000000000000a799b806020e0828" Message-ID-Hash: JO55SGCZ66LQYG7OPM5PSVULC3C3K2SK X-Message-ID-Hash: JO55SGCZ66LQYG7OPM5PSVULC3C3K2SK X-MailFrom: wlosh@bsdimp.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; 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: emacs List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000a799b806020e0828 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 3, 2023, 6:19 PM Adam Thornton wrote: > There are certainly teco implementations for Unix, although I don't know > if it was ever anyone's default editor anywhere. Indeed, there are > multiple implementations: I switched from a C teco implementation to pyte= co > in the Rubin Science Platform JupyterLab implementation (its utility is o= f > course dubious, but this is part of both my nefarious plan to make Jupyte= r > not merely mean "Julia, Python, and R", but to use that "e" -- and > reassociate it with the "t" -- by making it mean "Julia, Python, Teco, an= d > R", and also to include an easter egg for a fellow project member who is = a > teco fan). > > The first Emacs I used was GNU emacs at already version...16 or > something? In 1989, on ... I don't remember what the main system I used = at > the UT Austin Chaos Lab was, actually; we had an SGI Iris, but that wasn'= t > the machine I did my editing on. But by 1989 it was certainly > well-available and established. > We used some stripped down emacs in 1985 on the vax 11/750 running 4.2bsd. I built micro emacs for my DEC Rainbow under MS-DOS in the same time period... Warner On Thu, Aug 3, 2023 at 5:04=E2=80=AFPM Will Senn wrot= e: > >> As a longtime user and lover of ed/ex/vi, I don't know much about emacs, >> but lately I've been using it more (as it seems like any self-respecting >> lisper, has to at least have a passing acquaintance with it). I recently >> went off and got MACLISP running in ITS. As part of that exploration, I >> used EMACS, but not just any old emacs, emacs in it's first incarnation = as >> a set of TECO macros. To me, it just seemed like EMACS. I won't bore you >> with the details - imagine lots of control and escape sequences, many of >> which are the same today as then. This was late 70's stuff. >> >> My question for the group is - when did emacs arrive in unix and was it = a >> full fledged text editor when it came or was it sitting on top of some >> other subssystem in unix? Was TECO ever on unix? >> >> Will >> > --000000000000a799b806020e0828 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Aug 3, 2023, 6:19 PM Adam Thornton <athornton@gmail.com> wrote:
There are certainly t= eco implementations for Unix, although I don't know if it was ever anyo= ne's default editor anywhere.=C2=A0 Indeed, there are multiple implemen= tations: I switched from a C teco implementation to pyteco in the Rubin Sci= ence Platform JupyterLab implementation (its utility is of course dubious, = but this is part of both my nefarious plan to make Jupyter not merely mean = "Julia, Python, and R", but to use that "e" -- and reas= sociate it with the "t" -- by making it mean "Julia, Python,= Teco, and R", and also to include an easter egg for a fellow project = member who is a teco fan).

The first Emacs I used was GNU emac= s at already version...16 or something?=C2=A0 In 1989, on ... I don't r= emember what the main system I used at the UT Austin Chaos Lab was, actuall= y; we had an SGI Iris, but that wasn't the machine I did my editing on.= =C2=A0 But by 1989 it was certainly well-available and established.

We use= d some stripped down emacs in 1985 on the vax 11/750 running 4.2bsd.=C2=A0 = =C2=A0I built micro emacs for my DEC Rainbow under MS-DOS in the same time = period...=C2=A0

Warner

On Thu, Aug 3, 2023 at 5:04=E2=80=AFPM Will Senn <= ;will.senn@gmail.com> wrote:
=20 =20 =20
As a longtime user and lover of ed/ex/vi, I don't know much about emacs, but lately I= 9;ve been using it more (as it seems like any self-respecting lisper, has to at least have a passing acquaintance with it). I recently went off and got MACLISP running in ITS. As part of that exploration, I used EMACS, but not just any old emacs, emacs in it's first incarnation as a set of TECO macros. To me, it just seemed like EMACS. I won't bore you with the details - imagine lots of control and escape sequences, many of which are the same today as then. This was late 70's stuff.

My question for the group is - when did emacs arrive in unix and was it a full fledged text editor when it came or was it sitting on top of some other subssystem in unix? Was TECO ever on unix?

Will
--000000000000a799b806020e0828--