From: "Ron Natalie" <ron@ronnatalie.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Old screen editors
Date: Tue, 29 Mar 2022 21:46:42 +0000 [thread overview]
Message-ID: <em3a43efbb-54b9-4e84-bfb0-d39121925111@alien> (raw)
In-Reply-To: <2305F69C-26A5-45C4-9F55-DC7A0ECE85BA@quintile.net>
Was it one of the awful Pukin-Elmer terminals. I hated those things.
Then there was the Rand/Interactive Systems INed. We were stuck using
that when I worked for Martin.
I never learned vi. If there is no EMACS-like thing on the machine,
then I just use ed (sometimes I can get by with ex/vi in line mode).
The funniest editor story I have is one day I'm working at Martin.
Having actually heard of UNIX before (let alone having done kernel and
other work) I was sort of the in house expert. One day one of my
coworkers calls out to me:
"What's all this Bell System crud in the editor?"
I'm thinking, well, it's all Bell System crud. What specifically are
we talking about. I walk around to see his terminal and find he has
been typing 1 repeatedly to the shell prompt invoking our /usr/bin/1
that said "One Bell System, It Works."
After that I modded the program to say "You're not in the editor,
Bernie."
It was almost as much fun as putting "You might have mail." in motd.
------ Original Message ------
From: "Steve Simon" <steve@quintile.net>
To: tuhs@minnie.tuhs.org
Sent: 3/29/2022 3:09:52 PM
Subject: Re: [TUHS] Old screen editors
>
>I never really used it but i do remember an editor called le on the v7 interdata/Perkin Elmer i used at Leeds poly.
>
>I read electronics and we all used vi, the computer science people at a different campus used le on their Interdata; no idea why.
>
>anyone any background on le? ihave not seen sight nor sound of it since.
>
>-Steve
>
next prev parent reply other threads:[~2022-03-29 21:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 19:09 Steve Simon
2022-03-29 21:46 ` Ron Natalie [this message]
2022-03-30 0:22 ` Tom Lyon via TUHS
-- strict thread matches above, loose matches on Subject: below --
2022-03-29 20:40 Noel Chiappa
2022-03-29 20:50 ` Phil Budne
2022-03-29 20:54 ` Ron Natalie
2022-03-30 5:41 ` Lars Brinkhoff
2022-03-30 7:50 ` Thomas Paulsen
2022-03-29 18:35 Noel Chiappa
2022-03-29 10:39 Noel Chiappa
2022-03-29 11:05 ` Rob Pike
2022-03-29 13:37 ` Clem Cole
2022-03-29 15:43 ` Angelo Papenhoff
2022-03-30 5:36 ` Lars Brinkhoff
2022-03-28 21:03 [TUHS] Alive? Warren Toomey via TUHS
2022-03-28 22:24 ` Bakul Shah
2022-03-28 23:23 ` Greg 'groggy' Lehey
2022-03-29 0:00 ` Bakul Shah
2022-03-29 0:31 ` [TUHS] Old screen editors Lawrence Stewart
2022-03-29 0:53 ` Charles H Sauer (he/him)
2022-03-29 8:29 ` Rob Pike
2022-03-29 13:24 ` Clem Cole
2022-03-29 8:34 ` George Michaelson
2022-03-29 8:40 ` arnold
2022-03-29 13:45 ` Clem Cole
2022-03-29 14:31 ` Andrew Hume
2022-03-29 14:35 ` arnold
2022-03-29 14:42 ` Andrew Hume
2022-03-30 0:59 ` Mary Ann Horton
2022-03-30 5:11 ` arnold
2022-03-29 12:45 ` Thomas Paulsen
2022-03-29 13:26 ` arnold
2022-03-30 8:37 ` Ralph Corderoy
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=em3a43efbb-54b9-4e84-bfb0-d39121925111@alien \
--to=ron@ronnatalie.com \
--cc=tuhs@minnie.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).