public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: L A Walsh <cygwin@tlinx.org>,
	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: Fri, 9 Apr 2021 15:41:06 +0100	[thread overview]
Message-ID: <3a23e83c-670b-c599-b77b-18074dadf42e@dronecode.org.uk> (raw)
In-Reply-To: <606CFC89.6030700@tlinx.org>

On 07/04/2021 01:27, L A Walsh wrote:
> I don't recall this always being this way as I keep running into
> a problem with my input going into the wrong window.
> 
> I've noted I seem to be relying on which editor(i.e. gvim)
> window in X11 has focus by noting that it has a
> blinking square cursor in the window at the cursor's
> current position in the edited text.
> 
> If I move the windows cursor to another editor window in X11,
> the blinking cursor moves to the new window, but if I move
> it to a native window, the blinking doesn't stop.
> 
> Has this always been this way?

I think so, yes.

See [1] et seq. for a discussion of what I think is the same problem, 
where the Cygwin X server doesn't notify X windows of a focus loss when 
the focus moves to a non-X window.

Unfortunately, my attempts at fixing this just introduced more problems 
(see [2],[3] et seq.), and so were reverted.

[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

  parent reply	other threads:[~2021-04-09 14:41 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 [this message]
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
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=3a23e83c-670b-c599-b77b-18074dadf42e@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@tlinx.org \
    /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).