The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Ratfor s
Date: Sun, 30 Jan 2022 12:02:38 -0500	[thread overview]
Message-ID: <CAC20D2PV_mR6Fu=aix4unEgnC78=7nduSa35QKPCqUz2HPkYyg@mail.gmail.com> (raw)
In-Reply-To: <87492671-3406-49DF-B458-5F701DDFC09B@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

On Sun, Jan 30, 2022 at 11:03 AM Will Senn <will.senn@gmail.com> wrote:

> Has anyone seen Fraser's original ratfor source for the s editor for unix
> on the PDP-11. It was a screen editor front-end built on top of Software
> Tools's edit. I've seen a c version, but I'm interested in the 375 line
> version :).


I'm not sure they are the same editor.  The C program called s is part of
Webb Miller's Software Tools Sampler and it's a full editor, not a front
end [see: Webb Miller's S Tiny VI editor <https://github.com/udo-munk/s>
].  By design, it is mostly vi compatible.  This paper from Chris Feazer
seems to be a front end for SWT editor, and was original done on the PDP-10
[which makes sense] and seems to be contemporary to the vi work at UCB and
in fact called back to the SWT editor (which was >>modeled<< on UNIX ed),
as opposed to ex/vi which are extensions to the v6 implementation of the
UNIX ed editor.

[-- Attachment #2: Type: text/html, Size: 1493 bytes --]

      parent reply	other threads:[~2022-01-30 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30 16:03 Will Senn
2022-01-30 16:09 ` arnold
2022-01-30 16:12   ` Will Senn
2022-01-31  7:13     ` arnold
2022-01-31  7:21       ` arnold
2022-01-31 20:22       ` Noel Hunt
2022-01-30 17:02 ` Clem Cole [this message]

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='CAC20D2PV_mR6Fu=aix4unEgnC78=7nduSa35QKPCqUz2HPkYyg@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=tuhs@tuhs.org \
    --cc=will.senn@gmail.com \
    /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).