From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Keyboards (was kbd.c)
Date: Sat, 30 Mar 2002 19:52:06 -0500 [thread overview]
Message-ID: <640398c2f7c7a6423c64ccf01454e132@plan9.bell-labs.com> (raw)
> I assume you mean 'only *non* destroyer size' below.
No, I mean destroyer size. It was in comparison to
the ``battleship size'' Windows keyboards. Perhaps I'm
misremembering the boat sizes in the game, but I thought
the destroyer was the shortest at 2 pegs long.
Russ
next reply other threads:[~2002-03-31 0:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-31 0:52 Russ Cox [this message]
2002-03-31 1:50 ` Digby Tarvin
2002-04-01 1:18 ` Dan Cross
2002-04-01 2:17 ` William Josephson
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 14:08 Russ Cox
2002-04-02 10:32 Ian Broster
2002-04-02 10:50 ` Lucio De Re
2002-04-01 3:12 plan9
2002-03-30 23:13 [9fans] kbd.c Russ Cox
2002-03-31 0:47 ` [9fans] Keyboards (was kbd.c) Digby Tarvin
2002-04-08 12:54 ` Ian Broster
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=640398c2f7c7a6423c64ccf01454e132@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).