9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "a pox on the things." [uk keyboards]
Date: Tue,  5 Feb 2002 12:45:39 +0100	[thread overview]
Message-ID: <3C5FC5E3.1B1A7F9F@strakt.com> (raw)
In-Reply-To: <20020205112826.5461c636.matt@proweb.co.uk>

Matt H wrote:
> but can't find out how to stop having to search my kb for the characters

Have you seen the /dev/kbmap stuff?

KBMAP(3)                                                 KBMAP(3)


NAME
       kbmap - keyboard map

SYNOPSIS
       bind -a #Io /dev

       /dev/kbmap

DESCRIPTION
       The kbmap device serves a one-level directory containing a
       single file, kbmap, representing the kernel's  mapping  of
       keyboard scan codes to Unicode characters (see cons(3) and
       keyboard(6)).

       Reads return the current contents of the map.  Each  entry
       is  one line containing three 11 character numeric fields,
       each followed by a space: a table number,  an  index  into
       the table (scan code), and the decimal value of the corre-
       sponding Unicode character (0 if none).  The table numbers
       are platform dependent; they typically distinguish between
       unshifted and shifted keys.   The  scan  code  values  are
       hardware dependent and can vary from keyboard to keyboard.

       Writes to the file change the map.  Lines written  to  the
       file  must  contain  three space-separated numeric fields,
       representing the table number, scan code index,  and  Uni-
       code  character.   Values  are  taken to be decimal unless
       they start with 0x (hexadecimal) or 0 (octal).   The  Uni-
       code character can also be represented as 'x where x gives
       the UTF-8 representation of the  character  (see  utf(6)).
       Entries in the Unicode `private use' area from +U'FD80' to
       +U'FDFF' might  have  special  meaning  to  some  keyboard
       drivers and should not be mapped (or remapped) lightly.

SEE ALSO
       cons(3), keyboard(6), utf(6)


  reply	other threads:[~2002-02-05 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 11:28 Matt H
2002-02-05 11:45 ` Boyd Roberts [this message]
2002-02-05 12:59   ` Matt H
2002-02-05 14:06     ` Boyd Roberts

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=3C5FC5E3.1B1A7F9F@strakt.com \
    --to=boyd@strakt.com \
    --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).