From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keymaps question. would this be acceptable for you all?
Date: Wed, 12 Nov 2003 12:45:44 +0100 [thread overview]
Message-ID: <1e3ac7475c67302f86694532b599f367@plan9.escet.urjc.es> (raw)
In-Reply-To: <011801c3a911$af3db1a0$b9844051@insultant.net>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
The one used while boot(8)ing was static (we're using the spanish layout).
The only compose shifts I need to detect are alt and altgr (left alt, right alt on us).
Since we get rid of compose in the kernel, I can simply put the key 'Alt'/AltGr before
any key being kbdputc for the user driver to know. Regarding shift and control, the
user driver already gets keys for shift-a control-a.
is there any other thing I'm missing?
thanks for your reply.
[-- Attachment #2: Type: message/rfc822, Size: 2182 bytes --]
From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] keymaps question. would this be acceptable for you all?
Date: Wed, 12 Nov 2003 12:39:50 +0100
Message-ID: <011801c3a911$af3db1a0$b9844051@insultant.net>
> As an extra benefit, we could get rid of the kernel code for devkbmap,
> static keymaps, and compose.
it was never really static. you just loaded the one you wanted.
you need various 'compose' shifts.
next prev parent reply other threads:[~2003-11-12 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 9:12 Fco.J.Ballesteros
2003-11-12 11:13 ` Boyd Roberts
2003-11-12 11:34 ` Fco.J.Ballesteros
2003-11-12 11:39 ` boyd, rounin
2003-11-12 11:45 ` Fco.J.Ballesteros [this message]
2003-11-12 12:02 ` boyd, rounin
2003-11-12 13:39 ` Fco.J.Ballesteros
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=1e3ac7475c67302f86694532b599f367@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).