From: "Jeffrey H. Johnson" <trnsz@pobox.com>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Software Archeology: QED
Date: Sun, 7 Oct 2018 23:58:27 -0400 [thread overview]
Message-ID: <F220EBBB-7AA5-41AD-9739-36333B0F3DE3@pobox.com> (raw)
In-Reply-To: <A5B0EEC4-9AC1-4E7D-8D26-DEEFAF4DAD2C@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Might as well send this to the list:
There are Multics QEDX sources, but I haven't run across QED - however, there is an overview of it's use and commands in the General Electric June 1969 Multics Condensed Guide (http://bitsavers.org/pdf/honeywell/multics/swenson/6906.multics-condensed-guide.pdf)
I pulled the QEDX source at put it at https://ban.ai/~jhj/misc/qedx/ for easy access - this is the MR12.5 version and last modified in 1989, sadly, I don't ever recall seeing the BCPL QED. [ I'll be sure to remember now if I see it. ]
[ Somewhat off-topic ] How about Yale 'Z' as long as we're talking editors? Or another editor (that I very much like) is the 'G' editor, which has a long history, originating on Honeywell 6000 GCOS/TSS, originally written in B: https://github.com/ascheepe/g-editor - works nicely today. There is also the Ecce editor, which includes versions in IMP, BASIC, C, BCPL, and FORTRAN at http://history.dcs.ed.ac.uk/archive/apps/ecce/ - bringing Ecce up on Multics is an item on my todo list.
-- Jeff - https://ban.ai/multics/
[-- Attachment #2: Type: text/html, Size: 1989 bytes --]
next parent reply other threads:[~2018-10-08 3:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A5B0EEC4-9AC1-4E7D-8D26-DEEFAF4DAD2C@pobox.com>
2018-10-08 3:58 ` Jeffrey H. Johnson [this message]
2019-02-04 20:53 Christopher Browne
-- strict thread matches above, loose matches on Subject: below --
2018-10-25 22:47 Noel Chiappa
2018-10-10 19:21 Norman Wilson
2018-10-07 6:07 arnold
2018-10-07 10:05 ` Lars Brinkhoff
2018-10-07 10:23 ` Arrigo Triulzi
2018-10-07 12:33 ` Donald ODona
2018-10-07 12:46 ` Steve Nickolas
2018-10-07 13:20 ` jsteve
2018-10-07 12:52 ` Arrigo Triulzi
2018-10-08 10:18 ` KatolaZ
2018-10-07 16:41 ` Jonathan Gevaryahu
2018-10-07 12:41 ` Donald ODona
2018-10-07 14:11 ` arnold
2018-10-07 15:41 ` Donald ODona
2018-10-07 15:52 ` Leah Neukirchen
2018-10-07 17:00 ` Lars Brinkhoff
2018-10-07 17:11 ` Lars Brinkhoff
2018-10-08 3:21 ` Lars Brinkhoff
2018-10-08 19:00 ` Jeremy C. Reed
2018-10-25 6:56 ` Donald ODona
2018-10-25 16:09 ` Lars Brinkhoff
2018-10-25 21:15 ` Noel Hunt
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=F220EBBB-7AA5-41AD-9739-36333B0F3DE3@pobox.com \
--to=trnsz@pobox.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).