From: Andrew Hume <andrew@humeweb.com>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: the Courier font family and nroff history
Date: Mon, 25 Mar 2024 12:15:50 -0700 [thread overview]
Message-ID: <86CB6E4C-A3E4-4DE6-88CE-1BFBC408CC86@humeweb.com> (raw)
In-Reply-To: <A78A07AE5F3B40F1B321BEDFBBBCD09A.for-standards-violators@oclsc.org>
i work with tom, and he claims that he (tom) did the imagen messaging stuff.
i sill don’’t know who did the 202 handler code, even tho i was
the designated main handler of the paper and goo for the 202.
> On Mar 23, 2024, at 10:08 AM, Norman Wilson <norman@oclsc.org> wrote:
>
> Bill Cheswick:
>
>> The Unix room text-to-speech device used to announce:
>>
>> "Ding ding ding. Please add goo. This doesn’t happen very often."
>
> Since we're all nerds here, I feel compelled to correct this.
>
> The actual announcement was
>
> Help! Please add goo!
>
> The suffix was applied to a different message:
>
> Please add toner. You won't have to very often.
>
> `Goo' was some sort of pre-mix that needed frequent topping up.
> Hence `you won't have to very often,' to remind you which was which.
>
> Other messages included
>
> Please add paper.
> Printer check lamp is lit. What do you want to do about it?
> Service check lamp is lit. You're in big trouble now!
>
> All these messages were designed by Tom Killian, who wrote the
> local code that controlled the 202.
>
> Norman Wilson
> Toronto ON
next prev parent reply other threads:[~2024-03-25 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 15:37 Douglas McIlroy
2024-03-23 16:03 ` William Cheswick
2024-03-23 17:08 ` Norman Wilson
2024-03-23 20:56 ` Rob Pike
2024-03-23 22:53 ` Rich Salz
2024-03-25 19:15 ` Andrew Hume [this message]
2024-03-23 16:36 ` G. Branden Robinson
[not found] <171123441022.817627.11524835891647187739@minnie.tuhs.org>
2024-03-23 23:05 ` Paul McJones
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=86CB6E4C-A3E4-4DE6-88CE-1BFBC408CC86@humeweb.com \
--to=andrew@humeweb.com \
--cc=norman@oclsc.org \
--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).