From: Nicolas Mailhot <Nicolas.Mailhot@laposte.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Keyboard oddness.
Date: Fri, 26 Sep 2003 16:12:47 +0200 [thread overview]
Message-ID: <1064585567.23200.15.camel@ulysse.olympe.o2t> (raw)
In-Reply-To: <20030926134116.GA9721@ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]
Le ven 26/09/2003 à 15:41, Vojtech Pavlik a écrit :
> On Fri, Sep 26, 2003 at 03:08:36PM +0200, Nicolas Mailhot wrote:
>
> > | > > > Couldn't it at least detect there's a problem ? Most people I know do not press a key
> > | > > > 2000+ times in a row during normal activity.
> > | > >
> > | > > You do. Scrolling up/down in a document is one example. And there is no
> > | > > point to limit the repeat to say 80 or 200 characters. You would still
> > | > > hate having 80 repeated characters and then it stopping.
> > | >
> > | > Well then only allow monster autorepeats for arrows then.
> > | > (they are never stuck in my board anyway;)
> >
> > | And j, k, w, b, ., all function keys, <bs>, <del>, <cr>,
> > | <sp>, <tab> and any other key used by any editor or game for
> > | navigation, level control or other function where the same
> > | key would be used scores of times in in rapid sequence.
> >
> > score << 2k+
> >
> > I wrote about monster autorepeats not every single duplicated keypress.
> > I fully agree it's stupid to expect detecting every single bogus repeat.
> >
> > However saying the system has no way to guess monster
> > autorepeats=problem is just plain wrong. There *are* thresholds after
> > which one can be 99% sure there is a problem (autorepeat gone mad or cat
> > sitting on the keyboard). No one is going to complain he has to release
> > a key every hundred or so repeats to confirm there's a human on the
> > other side of the keyboard.
>
> But what use would be this? You'd still get a screenful of 'j's for
> example, maybe only 200 instead of 2000, but where is the difference?
The difference being the system can then try to rescue my keyboard;)
Right now the only fix I have is to reboot the system because there is
precious little I can do with a stuck keyboard. Thank god software
reboot is always possible be it with the mouse or the acpi button.
(and this also solves the case when something falls on a keyboard which
does happen now and then. I don't mind a screen of j's when the
alternative is 200 j's screenfulls)
--
Nicolas Mailhot
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-26 14:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 9:43 Nicolas Mailhot
2003-09-26 10:24 ` Vojtech Pavlik
2003-09-26 10:41 ` Nicolas Mailhot
2003-09-26 10:51 ` Vojtech Pavlik
2003-09-26 12:48 ` jw schultz
2003-09-26 13:08 ` Nicolas Mailhot
2003-09-26 13:41 ` Vojtech Pavlik
2003-09-26 14:12 ` Nicolas Mailhot [this message]
2003-09-26 14:17 ` Vojtech Pavlik
2003-09-26 14:21 ` Nicolas Mailhot
2003-09-26 14:26 ` Vojtech Pavlik
2003-09-26 14:50 ` Nicolas Mailhot
2003-09-26 15:06 ` Vojtech Pavlik
2003-09-26 15:21 ` Nicolas Mailhot
2003-09-26 15:24 ` Vojtech Pavlik
2003-09-26 13:56 ` Helge Hafting
2003-09-26 14:01 ` Mike Dresser
2003-09-28 10:58 ` Helge Hafting
2003-10-02 12:40 ` Pavel Machek
2003-10-01 10:09 ` Pavel Machek
2003-10-01 13:06 ` Nicolas Mailhot
-- strict thread matches above, loose matches on Subject: below --
2003-09-20 20:33 Rob Landley
2003-09-20 22:18 ` Andries Brouwer
2003-09-21 18:51 ` Rob Landley
2003-09-21 10:04 ` Vojtech Pavlik
2003-09-21 20:20 ` Rob Landley
2003-09-22 20:06 ` Rob Landley
2003-09-22 22:06 ` Andries Brouwer
2003-09-23 0:23 ` Rob Landley
2003-09-23 10:51 ` Greg Louis
2003-09-25 23:59 ` Rob Landley
2003-09-26 1:27 ` Rob Landley
2003-09-26 8:15 ` Andries Brouwer
2003-09-26 8:43 ` Rob Landley
2003-09-26 8:46 ` Vojtech Pavlik
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=1064585567.23200.15.camel@ulysse.olympe.o2t \
--to=nicolas.mailhot@laposte.net \
--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
all inboxes | Powered by JetHome®