From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] sources contrib/axel/rushhour
Date: Mon, 24 Jul 2006 16:32:51 -0700 [thread overview]
Message-ID: <3e1162e60607241632ped51250rab506937fa77f4ae@mail.gmail.com> (raw)
In-Reply-To: <200607242125.k6OLPbS28342@zamenhof.cs.utwente.nl>
This is really cool...
On 7/24/06, Axel Belinfante <Axel.Belinfante@cs.utwente.nl> wrote:
> great. I've just uploaded an updated version that
> by default shows the familiar cars which makes it
> less 'cluttered'. it uses faces when invoked with '-f'
> or when the faces button 3 menu item is pressed.
>
> Axel.
>
> > nice game, I'm playing it right now.
>
> I wrote:
> > > I've combined pieces of sokoban and memo into rush hour
> > > http://en.wikipedia.org/wiki/Rush_Hour_%28board_game%29
>
next prev parent reply other threads:[~2006-07-24 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 14:12 Axel Belinfante
2006-07-24 17:02 ` Federico G. Benavento
2006-07-24 21:25 ` Axel Belinfante
2006-07-24 23:32 ` David Leimbach [this message]
2006-07-25 0:25 ` dmr
2006-07-25 13:45 ` Axel Belinfante
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=3e1162e60607241632ped51250rab506937fa77f4ae@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
/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).