From: "Gorka Guardiola" <paurea@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] gnugo port for plan9
Date: Wed, 17 Oct 2007 12:52:19 +0200 [thread overview]
Message-ID: <599f06db0710170352k64b3e6few5e1a6aa7c39be728@mail.gmail.com> (raw)
In-Reply-To: <775b8d190710162328k5cd78e30u615e9bc29266684a@mail.gmail.com>
I have a user interface which knows about the rules. It is just a
stupid user interface.
contrib/paurea/goban
button 1 whites
button 2 black
button 3 mark as dead
c count
u undo
It is a backport from something which I wrote for plan b. Not
specially fast, but readable implementation of the rules.
--
- curiosity sKilled the cat
next prev parent reply other threads:[~2007-10-17 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 6:23 Rob 'Commander' Pike
2007-10-17 6:28 ` Bruce Ellis
2007-10-17 10:52 ` Gorka Guardiola [this message]
2007-10-17 11:00 ` Andrés Domínguez
-- strict thread matches above, loose matches on Subject: below --
2007-10-17 14:40 Steve Simon
2007-10-16 18:48 andrey mirtchovski
2007-10-17 1:17 ` Lee Duhem
2007-10-17 5:49 ` Bruce Ellis
2007-10-17 5:53 ` andrey mirtchovski
2007-10-17 6:07 ` Bruce Ellis
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=599f06db0710170352k64b3e6few5e1a6aa7c39be728@mail.gmail.com \
--to=paurea@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).