Mail Archives: cygwin/2005/09/16/00:07:49
Luke Kendall wrote:
> On 15 Sep, Igor Pechtchanski wrote:
>
>> On Fri, 16 Sep 2005, Luke Kendall wrote:
>>
>>
>>>Has anyone else noted that in vi (either in a plain Cygwin window or in
>>>an rxvt window, in an X session or not, also in xterm), that if you hold
>>>down the CTRL key and press keys at intervals (like F to page down
>>>through a file), and wait four seconds before another key press it's as
>>>if you don't have CTRL pressed at all? You have to release it and press
>>>afresh.
>>
>> >
>>
>>>The same applies to "more": hold CTRL down and press f, and it beeps at
>>>you to indicate that's invalid; still hold CTRL down, wait 4 seconds,
>>>then press f again, and it pages forward.
>>
>> >
>>
>>>This behaviour has been present for years, BTW, it's not new.
>>
>>
>> I suspect it's not Cygwin-related. This sounds like the Windows "sticky
>> keys" accessibility feature -- if any modifier key is held for some period
>> of time (more than 8 seconds, I think), Windows offers to turn on sticky
>> keys. Even if the feature is disabled, the 8-second timer may be started
>> every time the key is pressed. I wouldn't be surprised if this is the
>> cause of the behavior you observe...
>> Igor
>
>
> I checked, but found that I have "Sticky keys" turned off in the control
> panel accessibility options.
>
> Also, I've timed it roughly and it's close to 4 seconds, not 8. And if
> it's due to this, wouldn't Larry have been able to reproduce it??
>
> I'm now checking with other Cygwin users here to see if we can see what
> controls the reproducibility. I'll let you know the results.
>
> (BTW, FWIW I'm running Windows XP sp1.)
>
> Regards,
>
> luke
>
>
Could it be in the firmware on the keyboard? Is it possible to try another?
Larry
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -