mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: dtor_core@ameritech.net
Cc: "Martin J. Bligh" <mbligh@mbligh.org>,
	Pavel Machek <pavel@ucw.cz>, Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Remove silly messages from input layer.
Date: Thu, 4 May 2006 20:14:08 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605041954490.20879@blonde.wat.veritas.com> (raw)
In-Reply-To: <d120d5000605041134k3d9f5934ne9e01f7108cb0271@mail.gmail.com>

On Thu, 4 May 2006, Dmitry Torokhov wrote:
> > > On Wed 03-05-06 22:44:04, Dave Jones wrote:
> > >
> > > >There are two messages in the input layer that seem to be
> > > >triggerable very easily, and they confuse end-users to no end.
> > > >"too many keys pressed? Should I press less keys?"
> 
> Also I don't understand what people have against this message, it's at
> KERN_DEBUG level after all.

I often type at the text console; and I like to see KERN_DEBUG messages;
but I do NOT like to see kernel messages telling me I've mistyped - they
don't hurt my pride, but they do mess up my screen.

If I hit a wrong key, it's normal for that wrong key to be echoed, not a
kernel message saying "Are you sure you didn't want to hit another key?".
If I don't hit a key hard enough, it's normal for that key not to be
echoed.  So why, if I happen to hit a combination of keys by mistake,
do I get that wretched "too many keys pressed" message?  The appropriate
response is for what is accepted to be echoed, and that is all.

I keep #ifdef ATKBD_DEBUG around both the messages Dave highlighted
(but I forget when it was that I used to get the second one); the -mm
tree has had the "too many keys" message commented out for many months.

Hugh

  parent reply	other threads:[~2006-05-04 19:14 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
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 [this message]
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=Pine.LNX.4.64.0605041954490.20879@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=davej@redhat.com \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.org \
    --cc=pavel@ucw.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

all inboxes | Powered by JetHome®