From: Henry Worth <haworth@ncal.verio.com>
To: Michel Dänzer <daenzerm@student.ethz.ch>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Linux keycodes and left cursor on Pismo
Date: Mon, 25 Sep 2000 14:01:24 -0400 (EDT) [thread overview]
Message-ID: <Pine.SOL.4.10.10009251358270.21969-100000@ncal.verio.com> (raw)
In-Reply-To: <39CE9B1F.84530732@student.ethz.ch>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 877 bytes --]
On Mon, 25 Sep 2000, Michel [iso-8859-1] Dänzer wrote:
> Henry Worth wrote:
>
> > >After switching to Linux keycodes (and Debian's i386 us keymap), the left
> > >cursor key doesn't generate a keycode anymore. Interestingly, it works in
> > >X with Xkb, but not without.
> > >
> > >Anyone else sees this?
> >
> > Check the dev and user archives, I think this has been discussed a
> > few times since the new input layer backport went in.
>
> I've searched the archives now with no luck.
>
> So, can anyone please solve my problem, even if it has been solved before? :)
>
>
Serach on keymap around the late-June through Aug. period. I don't
think any of them specifically addressed your left key problem, but
rather the need for new, and as of then non-existent, keymaps to use
the Linux keycodes mode.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-25 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-22 20:25 Linux keycodes and left cursor on Pismo Henry Worth
2000-09-22 21:49 ` Martin Costabel
2000-09-23 4:07 ` Henry Worth
2000-09-23 14:14 ` Michel Dänzer
2000-09-25 0:23 ` Michel Dänzer
2000-09-25 6:28 ` Martin Costabel
2000-09-25 20:35 ` Michel Dänzer
2000-09-26 13:01 ` Franz Sirl
2000-09-26 13:05 ` Michel Dänzer
2000-09-25 18:01 ` Henry Worth [this message]
2000-09-25 18:05 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2000-09-22 22:56 Iain Sandoe
2000-09-22 14:00 Michel Dänzer
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.SOL.4.10.10009251358270.21969-100000@ncal.verio.com \
--to=haworth@ncal.verio.com \
--cc=daenzerm@student.ethz.ch \
--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).