From: arnold@skeeve.com
To: will.senn@gmail.com, arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Ratfor s
Date: Mon, 31 Jan 2022 00:21:45 -0700 [thread overview]
Message-ID: <202201310721.20V7LjiB024836@freefriends.org> (raw)
In-Reply-To: <202201310713.20V7Dxxf023410@freefriends.org>
arnold@skeeve.com wrote:
> Thanks for the link. I skimmed it and will read it later.
>
> What struck me was the splitting of the editor into front and back ends
> that did not have to be on the same machine. Rob Pike used that design
> for "sam" somewhat later. I wonder if he got the idea from 's' or came
> up with it on his own... (Dough, thoughts?)
Typo (embarassment). Should be "Doug, thoughts?". Sigh.
> Thanks,
>
> Arnold
>
> Will Senn <will.senn@gmail.com> wrote:
>
> > Hi Arnold,
> >
> > It was mentioned in the STinP edit discussion, so of course, I had to go looking! Here's the referenced article by Fraser:
> >
> > https://archive.org/details/compact-portable-crt
> >
> > Will
> > Sent from my iPhone
> >
> > > On Jan 30, 2022, at 10:09 AM, arnold@skeeve.com wrote:
> > >
> > > 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 :).
> > >>
> > >> Will
> > >>
> > >> Sent from my iPhone
> > >
> > > I've never heard of this. Can you give some background please?
> > >
> > > Thanks,
> > >
> > > Arnold
next prev parent reply other threads:[~2022-01-31 7:22 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 [this message]
2022-01-31 20:22 ` Noel Hunt
2022-01-30 17:02 ` Clem Cole
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=202201310721.20V7LjiB024836@freefriends.org \
--to=arnold@skeeve.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).