The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ralph Corderoy <ralph@inputplus.co.uk>
To: Lawrence Stewart <stewart@serissa.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Old screen editors
Date: Wed, 30 Mar 2022 09:37:12 +0100	[thread overview]
Message-ID: <20220330083712.BB43D21D9C@orac.inputplus.co.uk> (raw)
In-Reply-To: <11FBF445-4956-427E-8751-60BF5CA88116@serissa.com>

Hi Lawrence,

> At some point we got ex/vi, but before that we got the “Rand Editor”
> re, which was a perfectly functional screen editor, if you squinted a
> bit.
>
> Does anyone here know the place of re in the history?

RAND's re from 1974 had become Ned, for New Editor by 1977 when Ned's
author, Walt Bilofsky, later founder of The Software Toolworks, wrote
RAND report R2176.  https://www.rand.org/pubs/reports/R2176.html

        Over the past few years Ned, a text editor utilizing the full
    capabilities of the CRT display, has been under development and in
    use at The Rand Corporation...

        The Ned editor runs on the PDP-11 series of computers under
    the UNIX operating system.  It uses a CRT display to provide a
    two-dimensional window into a text file...  ...rectangular portions of
    text may be opened, deleted, and moved about...  The set of operations
    may be expanded by user-provided or system-provided text-processing
    programs...  The screen may be divided into several editing windows...

Chapter 3 has the history of IDA-CRD → Yale Editor ‘E’ → RAND
editor ‘re’ → Ned.

-- 
Cheers, Ralph.

  parent reply	other threads:[~2022-03-30  8:47 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
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 [this message]
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

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=20220330083712.BB43D21D9C@orac.inputplus.co.uk \
    --to=ralph@inputplus.co.uk \
    --cc=stewart@serissa.com \
    --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).