9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pavel Mihaylov <bin@bash.info>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard maps
Date: Thu, 16 May 2002 00:34:28 +0300	[thread overview]
Message-ID: <1021498469.3079.20.camel@dator> (raw)
In-Reply-To: <2ddd507ce00ca87c2bcc7eb42e70c919@plan9.escet.urjc.es>

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

На 14 май 2002 г. (вторник), в 14.37 часа, Fco.J.Ballesteros писа:
> Two of my students ({jvergara,jgato}@gsyc.escet.urjc.es) have
> changed the keyboard driver to support static maps allowing
> to switch at run time between them using the function keys.
> 

In kbd.h Altgr is defined as 0x38 which disagrees with the other
shift-state keys (Shift, Ctrl, etc). This is apparently the reason to
use variable gr, needed to differentiate between Altgr and simply 0x38
(which is actually '8'). I've changed the definition of Altgr to
Spec|0x67 (right after the other shift keys) and removed gr. I also
removed last_altgr which seems to be unused. All that fixed a bug for me
- when using keymaps without Altgr (i.e. us map) right Alt was supposed
to work as the left one but after pressing it I could enter any
arbitrary character _before_ collecting of compose sequence begins. The
revised kbd.c and kbd.h are attached. Btw, isn't it wise to rename Latin
from kbd.h to something more meaningful, such as Compose, since
composing is used to enter much more than Roman-script based characters?

Pavel



[-- Attachment #2.1: Type: text/plain, Size: 317 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Disposition: attachment; filename=kbdfix.tgz
	Content-Type: application/x-gzip; name=kbdfix.tgz
	Content-Transfer-Encoding: base64

[-- Attachment #2.2: kbdfix.tgz.suspect --]
[-- Type: application/octet-stream, Size: 2732 bytes --]

  parent reply	other threads:[~2002-05-15 21:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14 17:37 Fco.J.Ballesteros
2002-05-15  9:05 ` Boyd Roberts
2002-05-15 21:34 ` Pavel Mihaylov [this message]
2002-05-16 10:02   ` Boyd Roberts
2002-05-18 19:57     ` Pavel Mihaylov
2002-05-21 10:43       ` Boyd Roberts
2002-05-21 11:35         ` Pavel Mihaylov
2002-05-14 18:50 andrey mirtchovski
2002-05-14 19:40 andrey mirtchovski
2002-05-14 20:15 rob pike, esq.
2002-05-14 21:36 rob pike, esq.
2002-05-16 10:00 Fco.J.Ballesteros
2002-05-16 11:06 nigel
2002-05-16 13:18 rob pike, esq.
2002-05-20  9:55 Joel Salomon
2002-05-21  8:47 ` Joel Salomon
2003-11-17 18:24 Fco.J.Ballesteros
2003-11-17 18:34 ` ron minnich
2003-11-17 18:41   ` Fco.J.Ballesteros
2003-11-17 19:56 ` mirtchov
2003-11-18  8:13   ` Fco.J.Ballesteros
2004-03-16 14:31 David Presotto
2005-11-01 21:48 Heiko Dudzus
2005-11-01 22:34 ` Russ Cox
2005-11-02 19:49   ` Heiko Dudzus

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=1021498469.3079.20.camel@dator \
    --to=bin@bash.info \
    --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).