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 14:39:57 +0100 [thread overview]
Message-ID: <e664866fda89ee54b8fb763a2f178b49@plan9.escet.urjc.es> (raw)
In-Reply-To: <013f01c3a914$ce9c5da0$b9844051@insultant.net>
>> Regarding shift and control, the user driver already gets keys for shift-a
> control-a.
>
> you are assuming where 'a' is. the scan codes [song] remain[s] the same.
No. Ctrl+[what would be a in the us] is reported as ctrl-a by the kernel.
If your keyboard says it should be ctrl-x, you remap it. But the still get the ctrl
reported.
What I try to say is that the maps no longer use scan codes. They use runes
(or control runes).
prev parent reply other threads:[~2003-11-12 13:39 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
2003-11-12 12:02 ` boyd, rounin
2003-11-12 13:39 ` Fco.J.Ballesteros [this message]
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=e664866fda89ee54b8fb763a2f178b49@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).