The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Andrew Hume <andrew@humeweb.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Bell Office Automation System (OAS)?
Date: Thu, 8 Dec 2022 13:03:21 -0800	[thread overview]
Message-ID: <B4DD10A2-6E44-4BE6-81C0-CA1CCED8D00B@humeweb.com> (raw)
In-Reply-To: <jTJIwMf52vsXi8-MvXhytA4QzHIn3UJuvYb633h5bkfol3jppF6Tr4zFZzsV2tjJzmU2BSVZXhMgE2e2vTuYDLdDbtl34xJZfRUlsAuIo3Y=@protonmail.com>

when it matters, i was a part of the OAS team. i was technical lead, cathie brooks was our supervisor,
and i can’t really remember the other folks. i wrote ef. it was not my proudest programming achievement.
but denis ritchie helped me out by being a test user.

	andrew

> On Dec 8, 2022, at 12:24 PM, segaloco via TUHS <tuhs@tuhs.org> wrote:
> 
> Good day all, this may be COFF instead, but I'm not joined over there yet, might need some Warren help/approval.
> 
> In any case, received that 3B20S 4.1 manual in good shape, unpacked it, and out fell a little tri-fold titled "The Office Automation System (OAS) Editor-Formatter (ef) Reference Card" emblazoned with the usual Bell Laboratories, non-disclosure note abut the Bell System, and a nice little picture of a terminal I can't identify as well as the full manual for this OAS leaning against it: "The Office Automation System (OAS)" with a nice big Bell logo at the bottom of the spine.
> 
> The latter is likely a manual I spotted in a video once and couldn't make out the name/title at the time, thought I was seeing another long-lost UNIX manual.  I've never heard of this before, and Google isn't turning up much as Office Automation System appears to be a general industry term.
> 
> I seem to recall hearing about ef itself once or twice, some sort of pre-vi screen editor from Bell methinks?  Not super familiar with it though, I just seem to recall reading about that before somewhere.
> 
> Anywho, dealing with a move in the near future that is hopefully into a home I own, so pretty distracted from that scanning I keep talking about, but hopefully when I'm settled in in a few months I can setup a proper scan bench in my new place and really go to town on things.
> 
> - Matt G.


  reply	other threads:[~2022-12-08 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 20:24 [TUHS] " segaloco via TUHS
2022-12-08 21:03 ` Andrew Hume [this message]
2022-12-11 17:40   ` [TUHS] " Ralph Corderoy
2022-12-12  6:38     ` Andrew Hume
2022-12-12 16:10       ` segaloco via TUHS

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=B4DD10A2-6E44-4BE6-81C0-CA1CCED8D00B@humeweb.com \
    --to=andrew@humeweb.com \
    --cc=segaloco@protonmail.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).