From: Andrew Hume <email@example.com>
To: Clem Cole <firstname.lastname@example.org>
Subject: Re: [TUHS] Old screen editors
Date: Tue, 29 Mar 2022 07:31:39 -0700 [thread overview]
Message-ID: <8CD4B839-ED11-4A97-8D9A-65F78A78FB43@humeweb.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]
this may be a consequence for using such a bland name for a screen editor,
but i wrote a screen editor called ’se’ in 1981-83, just after we had moved
from piscataway to murray hill.
it was part of an effort to do office automation style products for Unix,
and came in around the time Unix transitioned from System III through
System 4 through the early days of System V.
my se was not very good, but i did have denis ritchie as an early tester.
> On Mar 29, 2022, at 6:45 AM, Clem Cole <email@example.com> wrote:
> Arnold, I agree, I do remember seeing it on what I think was the PWB 4.0 tape. IMHO: it was before cshell, termcap, vi et al was released inside of the rest of the Bell System and there seemed to be sometimes "SW from BSD be bad/crude" 'tude. IIRC ber and mmp must have had it running on the Marx's brothers systems in Whippany. But he had vi, so I personally never used it.
> @Mary Ann - this would have been around the time you were in Columbus and starting the terminfo work. Do you have any memories?
> On Tue, Mar 29, 2022 at 5:29 AM <firstname.lastname@example.org <mailto:email@example.com>> wrote:
> Did anyone within the Bell System ever use a screen editor called 'se'?
> (NOT related to the Georgia Tech se editor [se-editor.org <http://se-editor.org/>]).
> I used this on a USG UNIX 4.0 system ~ 1982 when I did some contract
> programming at Southern Bell. I think it was originally written for
> the Vax but it had been squeezed to run on a PDP-11/70 also.
> I've mentioned this in the past, but it seems to been covered over
> by the sands of time, and that nobody else ever used it.
[-- Attachment #2: Type: text/html, Size: 3099 bytes --]
next prev parent reply other threads:[~2022-03-29 15:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 21:03 [TUHS] Alive? Warren Toomey via TUHS
2022-03-28 21:17 ` Hellwig Geisse
2022-03-28 21:21 ` Steve Nickolas
2022-03-28 21:27 ` Charles H Sauer (he/him)
2022-03-28 21:29 ` Larry McVoy
2022-03-29 1:14 ` Chet Ramey
2022-03-28 21:43 ` Dave Horsfall
2022-03-28 22:24 ` Bakul Shah
2022-03-28 23:23 ` Greg 'groggy' Lehey
2022-03-28 23:29 ` Andrew Hume
2022-03-28 23:56 ` George Michaelson
2022-03-29 0:00 ` Bakul Shah
2022-03-29 0:31 ` Greg 'groggy' Lehey
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 [this message]
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
2022-03-29 1:10 ` [TUHS] Alive? Steve Nickolas
2022-03-29 6:37 ` Henry Mensch
2022-03-29 20:46 ` Dave Horsfall
2022-03-29 21:53 ` John Cowan
2022-03-29 10:39 [TUHS] Old screen editors 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-29 18:35 Noel Chiappa
2022-03-29 19:09 Steve Simon
2022-03-29 21:46 ` Ron Natalie
2022-03-30 0:22 ` Tom Lyon via TUHS
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).