From: L A Walsh <cygwin@tlinx.org>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: X11 blinking cursor in text window like 'gvim' - only halts if moved-over another X11-win
Date: Sat, 10 Apr 2021 14:37:31 -0700 [thread overview]
Message-ID: <60721A9B.1000605@tlinx.org> (raw)
In-Reply-To: <6071F92E.5050802@tlinx.org>
On 2021/04/10 12:14, L A Walsh wrote:
> On 2021/04/09 07:41, Jon Turney wrote:
>
>> I think so, yes.
>>
> ===
>
>
> That's unfortunate. Well, I wasn't sure if it was new
> or old. At least its not some new problem. Sigh.
>
> Thanks for the backstory.
>
>
>> [1] https://sourceware.org/legacy-ml/cygwin/2017-04/msg00168.html
>> [2] https://sourceware.org/legacy-ml/cygwin/2017-04/msg00278.html
>> [3] https://sourceware.org/pipermail/cygwin/2017-May/232564.html
>>
---
I don't know if this was tried, but the only way to really do
it would be along the lines of detecting when windows had grabbed
control via its time -- for cygwin to use a timer to detect when it
lost control. Ex. in cygwin's blink routine, it would need to check
that it still had focus, and if it had lost it for longer than 50-75ms
(maybe configurable), assume cursor is over a Win-Window... May not
be worth the bother, but it might catch the problem?
next prev parent reply other threads:[~2021-04-10 21:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 0:27 L A Walsh
2021-04-07 18:46 ` Achim Gratz
2021-04-08 8:52 ` L A Walsh
2021-04-08 9:52 ` Lemke, Michael SF/HZA-ZIC2
2021-04-08 11:19 ` Andrey Repin
2021-04-15 19:10 ` Achim Gratz
2021-06-16 17:41 ` L A Walsh
2021-04-09 14:41 ` Jon Turney
2021-04-09 15:12 ` Thomas Wolff
2021-04-10 21:40 ` L A Walsh
2021-04-11 14:14 ` Jon Turney
2021-04-10 19:14 ` L A Walsh
2021-04-10 21:37 ` L A Walsh [this message]
2021-04-11 14:33 ` Jon Turney
2021-04-11 14:53 ` L A Walsh
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=60721A9B.1000605@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).