The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: vi in cooked mode?
Date: Sat, 5 Nov 2022 11:45:26 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.2211051137590.43868@aneurin.horsfall.org> (raw)
In-Reply-To: <Y2WjV/RuqqoW7OFL@mit.edu>

On Fri, 4 Nov 2022, Theodore Ts'o wrote:

> Yeah, same here, although my start was with the editor that came with 
> the PDP-8 disk operating system (using an ASR-35), the PDP-15's 
> foreground/background system (using a KSR-33), and the PDP-11's RT-11 
> running under TSX-plus (using VT-100's and DECwriter for the console).

I started off with TECO on RT-11; talk about cryptic...

> So when I finally got a chance to use Unix when I got to college, 
> /bin/ed was so similar to the line oriented editors I had used on the 
> various Digital systems I had a chance to use while growing up and in 
> high school, I never bothered to use vi.  It was either ed or emacs, 
> depending on how loaded the time-sharing systems I was using in my 
> freshman year.

Shortly after I switched to "ed" on the 11/40 someone brought out "em" 
(editor for mortals) which was sort of a screen editor: I recall saying 
"what a stupid command name" as it was only a fumble away from "rm" :-(

> Of course, once I had a chance to use a Vaxstation or the IBM PC/RT all 
> to myself, I jumped over to emacs and never looked back --- except when 
> I was recovering a system in single user mode, of course.

A boss of mine insisted that everyone had to learned "ed", because after a 
system crash it might be the only editor available; that, or having to 
dial in over a slow modem.

-- Dave

  reply	other threads:[~2022-11-05  0:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 19:43 [TUHS] " Diomidis Spinellis
2022-11-03 20:26 ` [TUHS] " Clem Cole
2022-11-03 20:27   ` Clem Cole
2022-11-03 20:55   ` Warner Losh
2022-11-03 21:34     ` Clem Cole
2022-11-03 22:28       ` Warner Losh
2022-11-03 22:52         ` Ron Natalie
2022-11-04  6:43       ` Lars Brinkhoff
2022-11-04 15:18         ` Dan Cross
2022-11-04 17:54           ` Lars Brinkhoff
2022-11-04 18:33   ` Ron Natalie
2022-11-04 23:42     ` Theodore Ts'o
2022-11-05  0:45       ` Dave Horsfall [this message]
2022-11-05  1:02         ` Larry McVoy
2022-11-05  1:25           ` Bakul Shah
2022-11-05  1:40             ` Larry McVoy
2022-11-05  2:31               ` Rich Salz
2022-11-05  3:44                 ` Bakul Shah
2022-11-05 18:34               ` Theodore Ts'o
2022-11-05  9:29           ` Otto Moerbeek via TUHS
2022-11-04 22:13 ` Mary Ann Horton
2022-11-03 20:17 Noel Chiappa

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=alpine.BSF.2.21.9999.2211051137590.43868@aneurin.horsfall.org \
    --to=dave@horsfall.org \
    --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).