From: Mary Ann Horton <email@example.com>
Subject: Re: [TUHS] Old screen editors
Date: Tue, 29 Mar 2022 17:59:04 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
se(1) is in my UNIX 5.0 manual, which was the internal version of System
V release 1. It makes sense that it would be the one Andrew wrote.
My recollection is that se was the result of Not Invented Here. There
was lots of demand for vi in the internal USG version of UNIX, and it
was present in exptools, but not the official distribution of UNIX.
(Lots of demand for emacs, too, also in exptools.) Rather than adopt one
of them, se was written. I think it appeared about UNIX 4.2.
My UNIX 5.0 manual also has vi(1). Once vi was installed, demand for se
went away. I'm not sure when it was dropped, but it's not in my SVID.
On 3/29/22 07:42, Andrew Hume wrote:
> alas, no.
> it should have been on some official source tapes, tho.
> it was part of some office automation set of software;
> maybe that was mentioned in the tapes.
> i too remember nothing about it. outside of doing it
> because management wanted it, i never optionally used it.
>> On Mar 29, 2022, at 7:35 AM, email@example.com wrote:
>> Cool! I bet this was it! It was on a System 4 system.
>> The commands were entered at the top of the screen. I remember almost
>> nothing else about it.
>> Is there any chance you still have the source?
>> Andrew Hume <firstname.lastname@example.org> wrote:
>>> 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.
next prev parent reply other threads:[~2022-03-30 1:06 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
2022-03-29 14:35 ` arnold
2022-03-29 14:42 ` Andrew Hume
2022-03-30 0:59 ` Mary Ann Horton [this message]
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).