public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Domen Puncer <domen@coderock.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	akpm@osdl.org
Subject: Re: 2.6.12-rc2: Compose key doesn't work
Date: Tue, 31 May 2005 01:03:44 +0200	[thread overview]
Message-ID: <429B9BD0.7000004@keyaccess.nl> (raw)
In-Reply-To: <20050526155344.GB3694@ucw.cz>

Vojtech Pavlik wrote:

> On Thu, May 26, 2005 at 11:45:09AM -0400, Wakko Warner wrote:

>>I also have a problem with 2.6.12-rcX and ps/2 keyboard.  I would say it's
>>the same key we're talking about.  It does not work at the console nor in X
>>(showkey at the console does not see it).  It works with a USB keyboard.  My
>>"compose" is mapped to the menu key beside the right windows key.
>>
>>I do wish they'd fix it, because I use this key (kinda like another ALT key)
>>more than my compose key (again, the menu key, not the right win logo key)
> 
>  
> This patch should fix it.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> ChangeSet@1.2229.1.9, 2005-04-04 15:37:45+02:00, vojtech@suse.cz
>   input: Fix fast scrolling scancodes in atkbd.c

ACK, thanks.

Rene.

  parent reply	other threads:[~2005-05-30 23:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10  9:52 2.6.12-rc2: Compose key doesn't work Rene Herman
2005-04-14 10:04 ` Domen Puncer
2005-05-26 12:23   ` Domen Puncer
2005-05-26 12:27     ` Vojtech Pavlik
2005-06-03 21:16       ` Wakko Warner
2005-06-03 21:37         ` Dmitry Torokhov
2005-05-26 15:45     ` Wakko Warner
2005-05-26 15:53       ` Vojtech Pavlik
2005-05-26 16:09         ` Wakko Warner
2005-05-30 14:25         ` Wakko Warner
2005-05-30 14:39           ` Vojtech Pavlik
2005-05-30 23:03         ` Rene Herman [this message]
2005-04-14 11:18 ` Kees Bakker

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=429B9BD0.7000004@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=akpm@osdl.org \
    --cc=domen@coderock.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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