From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] More kbmap information
Date: Mon, 22 Dec 2014 08:44:39 -0800 [thread overview]
Message-ID: <e0ff7052420a0ae49a677281b0be09ce@lilly.quanstro.net> (raw)
In-Reply-To: <8477CDFC-C09A-4612-98C4-16020B5E27D4@9srv.net>
On Mon Dec 22 08:29:52 PST 2014, a@9srv.net wrote:
> I don't think kbmap is going to give you what you want here. It's a
> really easy way to set the non-modifier keys, but which modifier keys
> do what is built into the underlying code. I don't think what you're
> after would be too challenging, though; start by taking a look at
> /sys/src/9/pc/kbd.c (assuming you're running a stock 32-bit kernel),
> in particular the kbdputsc function.
>
> That said, after taking a look at the specific keyboard layout you've
> described, I'd suggest living with the Plan 9 compose system for a
> while first. Most folks have found it remarkably comfortable, at
> least if your primary language doesn't vastly exceed what's on a
> keyboard (Japanese &c). I know I miss it when I'm on every other
> system.
one thing that is a bit unfortunate is that kbmap uses ibm pc scan codes.
at this point it would be more sensible to use the usb key codes, and
use the fact that there is a unique map of scan code to deal with ps/2
keyboards. this would allow more sensible specifications like leftshift
instead of whatever scan code left shift is. it would also be more sensible
for that to be the system keyboard interface, rather than the wierd
16-bit encoding that we've got. (it doesn't even properly deal with
full-size mac keyboards.)
i haven't done this for compaibility reasons, but it sure would be a good
gsoc project.
- erik
next prev parent reply other threads:[~2014-12-22 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 14:30 Adrian Regenfuss
2014-12-22 16:32 ` Anthony Sorace
2014-12-22 16:44 ` erik quanstrom [this message]
2014-12-23 14:47 ` Adrian Regenfuss
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=e0ff7052420a0ae49a677281b0be09ce@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).