The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: emacs
Date: Fri, 4 Aug 2023 12:19:00 -0400	[thread overview]
Message-ID: <CAC20D2PHvpz4K1pr-fCSCcTOyVQo-jJLDAZ5jEM6W8dv8930Bg@mail.gmail.com> (raw)
In-Reply-To: <20230804023639.A620218C080@mercury.lcs.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

I offered Ward Cunningham's TECO page in my earlier message - which has one
of my favorite quotes:  *"TECO Madness -- a moment of convenience, a
lifetime of regret".*

I also mention Cantrell's C/UNIX version: Video teco
<https://streaklinks.com/Bm-JfYsNjZmndQ2FbAL4U22k/http%3A%2F%2Fwww.copters.com%2Fteco.html>

If this was someone using teco recently, Paul's version is possible/likely
as it was in C and became the teco many of used for UNIX.
For a while, I could never quite decide if I liked it more than vi, but
since ed and vi were >>everywhere<< from the Cray-1 to a PC, I stopped
using TECO as it sometimes took a little effort to make it work (although
Paul was pretty careful) - but particularly on non-UNIX boxes (other than
VMS) it might not be so easy.  Since Oscar's PiDP-10 and Angelo's PDP-1
work, I'll need an editor again, so I may have to relearn it -- be
interesting to see how fast it comes back. 🤔

For systems with a C compiler, Ward Miller's s (which is a subset of vi -
https://github.com/udo-munk/s) has been my go-to.
I was playing with getting it running on V7 since it full video for a
VT-100.

ᐧ

On Thu, Aug 3, 2023 at 10:36 PM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:

>     > From: Rob Pike
>
>     > There was a guy in production at Google using Unix TECO as his main
>     > editor when I joined in 2002.
>
> Do you happen to know which version it was, or what it was written in?
>
> It must have been _somebody_'s re-implementation, but I wonder who or where
> (or why :-).
>
>         Noel
>

[-- Attachment #2: Type: text/html, Size: 3109 bytes --]

  parent reply	other threads:[~2023-08-04 16:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  2:36 Noel Chiappa
2023-08-04  2:42 ` Rob Pike
2023-08-04 16:19 ` Clem Cole [this message]
2023-08-05  4:09   ` George Michaelson
  -- strict thread matches above, loose matches on Subject: below --
2023-08-04  2:17 Noel Chiappa
2023-08-04  5:03 ` Jonathan Gray
2023-08-05  4:34 ` Jonathan Gray
2023-08-04  0:04 [TUHS] emacs Will Senn
2023-08-04  0:19 ` [TUHS] emacs Adam Thornton
2023-08-04  0:27   ` Rob Pike
2023-08-04  0:49     ` Larry McVoy
2023-08-04  1:00       ` Rich Salz
2023-08-04 13:25         ` Lars Brinkhoff
2023-08-04  0:32   ` Warner Losh
2023-08-04  1:23     ` Larry Stewart
2023-08-04 13:38       ` Ronald Natalie
2023-08-04  1:59     ` Will Senn
2023-08-04  2:26       ` Erik E. Fair
2023-08-04  0:39   ` Greg 'groggy' Lehey
2023-08-04  0:44 ` Clem Cole
2023-08-04  0:47   ` Clem Cole
2023-08-04  0:53   ` Warner Losh
2023-08-04  2:14   ` Dan Halbert
2023-08-04  2:18 ` Bakul Shah

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=CAC20D2PHvpz4K1pr-fCSCcTOyVQo-jJLDAZ5jEM6W8dv8930Bg@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).