From: Mary Ann Horton <mah@mhorton.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] First machine to run rogue?
Date: Fri, 9 Jul 2021 20:17:14 -0700 [thread overview]
Message-ID: <9d28ce46-f314-bc00-d2db-1f11b353b9f3@mhorton.net> (raw)
In-Reply-To: <CAEoi9W6-HvePqqLe=Yhh=_tRNPego98J3c3nD7oGjkqwgz9=rg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]
As I recall, Rogue began to appear in late 1980 or early 81 at Berkeley.
I primarily remember it on the Vax. But I thought Toy et al originally
wrote it at UCSB and then it came to UCB. It was written for the Arnold
curses, and served as the first major application to test it out.
I loved that game. Still do, although I rarely find time to play it
anymore. It's widely available on web emulators these days, just search
for "play rogue online". It will likely be the color DOS version, but it
plays roughly the same.
The source was widely available and widely customized. I think I brought
a copy with me to Bell Labs in 1981 where Bob Flandrena eventually
sprouted the "brogue" variant. Some of the monsters could eat into the
walls between rooms, and when there was a line of several chasing you
down a hallway, one or two of them would pull around to pass... Brogue
worked on my new curses, it was in effect part of the test suite.
Eric, of course, is the authority noting that ing70 was "i" and, as I
recall, ingvax was "j".
Mary Ann
On 7/2/21 2:09 PM, Dan Cross wrote:
> On Fri, Jul 2, 2021 at 9:07 AM Clem Cole <clemc@ccc.com
> <mailto:clemc@ccc.com>> wrote:
>
> On Fri, Jul 2, 2021 at 8:15 AM Dan Cross <crossd@gmail.com
> <mailto:crossd@gmail.com>> wrote:
>
> It is; it looks like it was first distributed with
> 4.3BSD-Tahoe. The sources there are listed as "public domain
> rogue", but I'm not sure about the provenance of that code.
>
> That sounds right, you should ask Ken Arnold offline, I bet he had
> a better idea.He would have made them available to Keith.
>
>
> Great idea. I reached out on linked in, but don't have an email
> address for Ken. Anyone have his contact information?
>
> I'm curious if e.g. Mary Ann has any thoughts here, since she took
> over maintaining curses at some point and might have gotten some of
> the inside story?
>
> Thanks for the responses so far, all.
>
> - Dan C.
>
[-- Attachment #2: Type: text/html, Size: 4338 bytes --]
next prev parent reply other threads:[~2021-07-10 3:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 2:05 Dan Cross
2021-07-02 2:51 ` Clem Cole
2021-07-02 11:24 ` Dan Cross
2021-07-02 11:40 ` arnold
2021-07-02 12:14 ` Dan Cross
2021-07-02 13:07 ` Clem Cole
2021-07-02 15:24 ` Brad Spencer
2021-07-02 16:27 ` Adam Thornton
2021-07-02 21:09 ` Dan Cross
2021-07-10 3:17 ` Mary Ann Horton [this message]
2021-07-10 4:00 ` Erik E. Fair
2021-07-10 5:04 ` Jon Forrest
2021-07-10 21:09 ` Mary Ann Horton
2021-07-02 13:11 ` Bakul Shah
2021-07-02 13:22 ` Richard Salz
2021-07-03 1:10 ` Dan Cross
2021-07-02 13:04 ` Clem Cole
2021-07-13 17:48 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-07-03 2:21 ` Matt Day
2021-07-03 14:15 ` Clem Cole
2021-07-03 15:08 ` Warner Losh
2021-07-03 22:25 ` Eric Allman
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=9d28ce46-f314-bc00-d2db-1f11b353b9f3@mhorton.net \
--to=mah@mhorton.net \
--cc=tuhs@minnie.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).