linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: anthony tong <atong@uiuc.edu>
To: Jerry Quinn <jquinn@nortelnetworks.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Ideas on improving powercomputing keyboard
Date: Tue, 27 Jul 1999 12:36:52 -0500	[thread overview]
Message-ID: <19990727123652.A10314@mango.aol.edu> (raw)
In-Reply-To: <14237.54703.12309.139409@gargle.gargle.HOWL>; from Jerry Quinn on Tue, Jul 27, 1999 at 11:52:15AM -0400


Jerry Quinn (Tue, Jul 27, 1999 at 11:52:15AM -0400):
> Hi, all.  I'm finally annoyed enough by the 'a' chars generated by the caps
> lock key on power computing keyboards under X to try to fix it.  In the
> process, maybe it will be useful enough to actually swap it to be the control
> key (as any good keyboard should be :-).

Didn't a patch from Fred Bacon get into on of the DR2 updates to take
care of this? I forget how it worked around this problem, but I can
did it up if you can't find it.

> from the keys.  So the first question is - can I trust the output of showkeys?

Generally, yes, with showkeys -s

> What is RAW mode?  When is raw mode versus non-raw used and should the
> behavior I describe be any different in the two cases?  Does raw vs. non-raw
> explain why 'a's appear when pressing capslock in X but not at the console?

I think that we should figure out why it behaves properly at the
console first. I remember Paul M mentioning something about that but
I don't really recall the specifics.

On another note Franz Sirl mentioned that a capslock (with an apple
adjustable keyboard, I think) keypress generates extraneous capslock
up/down events in X.


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  parent reply	other threads:[~1999-07-27 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-27 15:52 Ideas on improving powercomputing keyboard Jerry Quinn
1999-07-27 16:06 ` Geert Uytterhoeven
1999-07-27 16:45   ` Jerry Quinn
1999-07-27 17:36 ` anthony tong [this message]
1999-07-27 18:28   ` David A. Gatwood
1999-07-27 19:21   ` Jerry Quinn

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=19990727123652.A10314@mango.aol.edu \
    --to=atong@uiuc.edu \
    --cc=jquinn@nortelnetworks.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).