From: Pavel Machek <pavel@ucw.cz>
To: Dave Jones <davej@redhat.com>,
dtor_core@ameritech.net, "Martin J. Bligh" <mbligh@mbligh.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Remove silly messages from input layer.
Date: Fri, 5 May 2006 12:31:23 +0200 [thread overview]
Message-ID: <20060505103123.GB4206@elf.ucw.cz> (raw)
In-Reply-To: <20060504183840.GE18962@redhat.com>
On Čt 04-05-06 14:38:40, Dave Jones wrote:
> On Thu, May 04, 2006 at 02:34:34PM -0400, Dmitry Torokhov wrote:
>
> > >Perhaps it should say that then ;-)
> >
> > Do you have a beter wording in mind? "Keyboard reports too many keys
> > were pessed at once, some keystrokes might be dropped"?
>
> It still doesn't make sense when the user only pressed a single key,
> or in some cases, never pressed *any* key (don't have that report to hand,
> but it was a laptop keyboard)
If you only pressed single key -- your keyboard is crap or there's
some problem in the driver.
If you never pressed any key -- your keyboard is crap or there's
some problem in the driver.
...in both of these cases the message is actually useful. Where it is
not useful is when cat walks over your keyboard, because you can
actually expect this message when pressing 10 keys at once.
...in both of these cases failure should be investigated to find out
what is going on.
OTOH for example I now know that capslock-x-c is combination X32 does
not like. Unfortunately, if you swap capslock and ctrl, and type too
fast... you'll press this combination while exiting emacs.
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-05-05 10:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 2:44 Dave Jones
2006-05-04 7:13 ` Pavel Machek
2006-05-04 7:17 ` Pavel Machek
2006-05-04 15:08 ` Martin J. Bligh
2006-05-04 18:34 ` Dmitry Torokhov
2006-05-04 18:38 ` Dave Jones
2006-05-05 10:31 ` Pavel Machek [this message]
2006-05-05 10:39 ` Sergei Organov
2006-05-05 10:51 ` Valdis.Kletnieks
2006-05-05 15:27 ` Dave Jones
2006-05-05 15:37 ` Martin Mares
2006-05-05 15:46 ` Dave Jones
2006-05-05 15:54 ` Martin Mares
2006-05-05 16:00 ` Dave Jones
2006-05-05 16:12 ` Martin Mares
2006-05-05 19:59 ` Nuri Jawad
2006-05-05 20:06 ` Martin Bligh
2006-05-05 20:30 ` Nuri Jawad
2006-05-07 8:07 ` Joseph Fannin
2006-05-08 6:43 ` Helge Hafting
2006-05-08 7:25 ` Con Kolivas
2006-05-09 6:54 ` Helge Hafting
2006-05-04 19:14 ` Hugh Dickins
2006-05-04 15:45 ` David Greaves
2006-05-06 18:51 ` Jindrich Makovicka
2006-05-04 14:59 ` Nuri Jawad
2006-05-04 19:24 ` Hua Zhong
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=20060505103123.GB4206@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=davej@redhat.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.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
all inboxes | Powered by JetHome®