From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: mintty slow feedback in keyboard auto repeat mode
Date: Wed, 3 Jun 2020 22:41:10 +0200 [thread overview]
Message-ID: <cc64b2c5-2287-e9df-0cad-4de0e414c705@towo.net> (raw)
In-Reply-To: <CAEATi-Gw8FSuovp5icv76=LXoM=-1__yrDwrFrAOffuratFL0A@mail.gmail.com>
Am 03.06.2020 um 22:11 schrieb Michal Grodzki via Cygwin:
> Hi,
>
> mintty has slow keyboard feedback in auto repeat mode.
This has already been fixed; 3.1.7 coming this week.
> Version 3.1.4-1
> works correctly. The problem arises from version 3.1.5-1 and it exists in
> 3.1.6-1. Now I use the old 3.1.4-1 version because of it.
>
> I can reproduce this issue on demand by reinstalling mentioned versions of
> mintty in setup GUI. I do not change anything more. It is quite a fresh and
> minimal installation of Cygwin.
>
> My standard keyboard speed settings in Control Panel / Keyboard / Speed tab:
> repeat delay: the shortest
> repeat rate: the fastest
>
> The best way to reproduce this I think is to simultaneously open notepad
> and mintty session.
> Please hold down a key and recognize the speed of printed characters and
> compare their speed in notepad and mintty session.
>
> My configuration:
> laptop HP ProBook 640 G2, Windows 10 Enterprise 64-bit Version:
> 17763.1217, Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 8 GB RAM; Cygwin
> installed with “just for me” option in a subfolder placed in my Windows
> desktop.
>
> Should I change something in Mintty settings to achieve fast keyboard
> feedback in auto repeat mode? Is this case related to software changes?
>
> Thanks,
> Michal Grodzki
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2020-06-03 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 20:11 Michal Grodzki
2020-06-03 20:41 ` Thomas Wolff [this message]
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=cc64b2c5-2287-e9df-0cad-4de0e414c705@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).