Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bounce Keys-- How to set from CLI

252 views
Skip to first unread message

William Unruh

unread,
Apr 11, 2015, 4:56:26 PM4/11/15
to
I want the bounce keys option (X/KDE/accessibility) but the option in
the KDE System Settings mins out at 100ms, which is too long. When I
type two letters the same (as in Letters, or keep, of silly) it is
probably about 70ms between the two presses. Thus I would like to set it
at 50ms. Is there some way of setting this time without going through
SystemSettinghs->Accessibility which has that 100 ms limit? Is there
some command line utility to do so?
The setting is listed in .kde4/share/config/kaccesrc and I can change it
from 100 to 50 in that, but, the SystemSettings keeps changing it back
and it only takes effect on restarting KDE if I change it in the file,
neither of which I want. I would like to run some cli program ( like
synclient for the Synaptics Touchpad options) to change that setting
immediately.
Does anyone know of such a program?


Doug Laidlaw

unread,
Apr 14, 2015, 12:10:30 PM4/14/15
to
xset is installed on mine. For syntax, see
http://linuxforcynics.com/how-to/set-keyboard-repeat-delay-and-rate

HTH,

Doug.

William Unruh

unread,
Apr 14, 2015, 7:13:00 PM4/14/15
to
That seems to be the opposite of what I want. Ie, I can use xset to
determine when holding down a key starts to repeat that key. That is not
my problem. My repeat delay is about 200ms and is fine. The bounce keys
is if the key gets hit twice in row (or thinks it is because of lousy
electronics) I want to supress double key strokes if they occur on a
time scale of less than say 1/20 of a second. key repeat delay does
nothing about that.

Doug Laidlaw

unread,
Apr 14, 2015, 9:46:41 PM4/14/15
to
William Unruh <un...@invalid.ca> Wrote in message:
> On 2015-04-14, Doug Laidlaw <do...@douglaidlaw.net> wrote:
>> William Unruh wrote:
>> xset is installed on mine. For syntax, see
>> http://linuxforcynics.com/how-to/set-keyboard-repeat-delay-and-rate
>
>
> That seems to be the opposite of what I want. Ie, I can use xset to
> determine when holding down a key starts to repeat that key.
>

Sorry, I misunderstood your question.

Doug.
--

Daniel47

unread,
Apr 15, 2015, 6:28:24 AM4/15/15
to
So your system is set up to suppress repeats (i.e. double key presses)
if they occur with-in 200mS, but you want to be able to reduce the time
between legitimate keystrokes to 50mS.

Sure seems to me you want to reduce the 200mS to the 50mS or slightly less.

Daniel

William Unruh

unread,
Apr 15, 2015, 7:37:27 AM4/15/15
to
There are two separate things. If a key is pressed twice in rapid
succession, do two copies of that letter get sent to the OS, or only
one. I want only one sent if the time between the presses is less than
50ms. The other is, if the key is pressed down and held down for 200 ms,
are many copies of that key sent to the operating system. That is I
believe what you are refering to.
So rapid double press, or long single press. They are different things.
The Accessibillity under System Settings allows one to suppress the
former, but the time is too long. The minimum time between two presses
there is 100ms, which also suppresses legitimate double presses (see
that word just before the parenthesis). I cannot double press faster
than about 70ms. However a fault in the keyboard (bounce) can repeat the
key faster. I want to suppress those but not my own double press of the
key.


>
> Daniel
>

Jim Beard

unread,
Apr 15, 2015, 9:29:08 AM4/15/15
to
Change to the Gnome desktop and use its bounce key enable? You go to the
Gnome Universal Access/Typing Assist (Access X) to Bounce Keys On/Off and
On allows you to use a slider to set the delay. Set to minimum delay I
could hit the same key twice and get only one accepted only if I tried
very hard to do so.

Have you tried changing the value in kaccesrc and then changing ownership
to root, or maybe just make the file read only with chmod 444 kaccesrc?
This could complicate other matters but should solve the problem of
SystemSetting setting it back.

Cheers!

jim b.

--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.
0 new messages