From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] kernel mk
Date: Sun, 30 May 2004 01:34:11 +0200 [thread overview]
Message-ID: <023e01c445d5$72783e50$347e7d50@SOMA> (raw)
In-Reply-To: <ee9e417a04052916296a2313d1@mail.gmail.com>
> of mk 9pcf when the default isn't right, i think i
> tried to remove this once and the metarules you'd have
> to write end up applying to too much.
my findings exactly.
damn ec2t doan work, but i'll play with it tomorrow.
being able to type azerty is a big win. in fact i found
myself typing qwerty on it.
i would suggest that kbmap, if it exixts, be bound, by default, to /dev
next prev parent reply other threads:[~2004-05-29 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 23:12 boyd, rounin
2004-05-29 23:29 ` Russ Cox
2004-05-29 23:34 ` boyd, rounin [this message]
2004-05-29 23:35 ` Geoff Collyer
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='023e01c445d5$72783e50$347e7d50@SOMA' \
--to=boyd@insultant.net \
--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).