9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: George Bronnikov <goga@rubinstein.mccme.ru>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] kbd.c
Date: Sun, 31 Mar 2002 22:32:31 +0400	[thread overview]
Message-ID: <Pine.LNX.4.30.0203312221490.6531-100000@donkey.bronnikov.mccme.ru> (raw)
In-Reply-To: <beb8d372d1f41bd0329973bccaf865a6@plan9.bell-labs.com>

On Sat, 30 Mar 2002, rob pike, esq. wrote:

> > My favourite keyboard, the Happy Hacking keyboard, doesn't have a caps
> > lock key, so I'd prefer a mechanism that doesn't require one.  The HH
> > keyboard does have alt and Б≈┼ keys, plus the usual array of function
> > keys, arrow keys and misc. weird PC keys (scroll lock, home, insert)
> > on other keys when the "function" modifier key is applied.
> Whatever your personal taste, the HH keyboard is a crock.  I think
> it's a mistake to go in one direction or the other based on that
> oddball.  The vast majority of keyboards have a caps lock and I think
> it's reasonable to assume one is present.

I needed some sticky modifier key to switch between Cyrillic and Latin;
in fact, nothing is tied to it being Caps Lock.  If HH does not have one,
you can choose any key you want and make it send the caps lock code -- the
kbmap mechanism allows that.

Perhaps the caps_lock variable should simply be renamed to something
like sticky_mod.

My solution will not work, of course, if you have more than two layouts
to switch (I've seen English/Russian/Ukrainian keymaps for Linux, for
example).  It is not hard to make an arbitrary number of keytables, but
I'm not sure it is worth the complexity.

	Goga



  parent reply	other threads:[~2002-03-31 18:32 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-30 21:28 rob pike, esq.
2002-03-30 22:41 ` Richard
2002-03-30 22:47 ` Digby Tarvin
2002-03-31 11:26   ` kazumi iwane
2002-03-31 12:21     ` kazumi iwane
2002-03-31  2:47 ` kazumi iwane
2002-03-31 18:32 ` George Bronnikov [this message]
2002-04-01  0:47   ` Boyd Roberts
2002-04-01  6:50     ` George Bronnikov
2002-04-01  7:22       ` Lucio De Re
2002-04-01 11:35         ` Boyd Roberts
2002-04-01 16:27         ` kazumi iwane
2002-04-01 16:33           ` Lucio De Re
2002-04-01 11:34       ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2002-04-02 10:48 forsyth
2002-04-02 10:56 ` Lucio De Re
2002-04-02 10:42 forsyth
2002-04-08 12:54 ` Andries Brouwer
2002-04-02  9:31 forsyth
2002-04-02  9:44 ` Boyd Roberts
2002-04-02  8:28 Fco.J.Ballesteros
2002-04-02  8:17 Fco.J.Ballesteros
2002-04-02  5:04 plan9
2002-04-02  1:58 okamoto
2002-04-01 14:01 rob pike, esq.
2002-04-01  1:54 okamoto
2002-04-01  1:40 okamoto
2002-03-31 19:35 andrey mirtchovski
2002-03-31 14:48 bwc
2002-03-31 15:13 ` Boyd Roberts
2002-03-31 17:06 ` Digby Tarvin
2002-03-31 10:24 forsyth
2002-03-31  5:40 rob pike, esq.
2002-03-30 23:13 Russ Cox
2002-03-30 21:20 Geoff Collyer
2002-04-08 12:47 ` Matthew C Weigel
2002-03-30 21:10 rob pike, esq.
2002-03-30 21:08 rob pike, esq.
2002-03-31 18:58 ` FJ Ballesteros
2002-04-01  0:36   ` Boyd Roberts
2002-04-01  0:42   ` Boyd Roberts
2002-03-23 12:01 George Bronnikov
2002-03-30 21:05 ` FJ Ballesteros
2002-03-31 12:45   ` 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=Pine.LNX.4.30.0203312221490.6531-100000@donkey.bronnikov.mccme.ru \
    --to=goga@rubinstein.mccme.ru \
    --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).