From: Jon Turney <jon.turney@dronecode.org.uk>
To: moss@cs.umass.edu, The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: New Windows open behind current ones rather than in front
Date: Sun, 30 Oct 2022 12:21:23 +0000 [thread overview]
Message-ID: <831ebd6a-431e-9355-c8d6-8645e90e1180@dronecode.org.uk> (raw)
In-Reply-To: <c9e9f12a-05ca-48d3-e221-559f0a9e6885@cs.umass.edu>
On 14/10/2022 16:58, Eliot Moss wrote:
> Dear Cygwiners -
>
> I am having an issue under Windows 11 where new windows, when spawned
> from the command line of (say) Cygwin bash or WSL2 bash come up *behind*
> current Windows. This behavior seems new to Windows 11. Anybody know a
> setting or technique to control / change this? Two examples:
>
> - Spawn Word from Cygwin bash
> - Spawn okular from WSL 2
>
> If I spawn xterm from Cygwin bash, it comes up in front, but from WSL2
> bash, it comes up behind. My X server is the Cygwin one. Happy to
> provide more details if this is not enough.
I have seen something like this on occasion with windows created by the
Cygwin X server, but that seems to be associated with having "focus
follows mouse" mode turned on.
I'm not sure if that os some problem in the way that the X server
manages the Z-order of it's windows, or something about the way that the
X server creates windows interacting with any 'focus stealing
prevention' heuristic that windows has (See 'ForegroundLockTimeout').
Your first example doesn't seem to involve X at all, so I guess that
points towards the second theory...
next prev parent reply other threads:[~2022-10-30 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 15:58 Eliot Moss
2022-10-30 12:21 ` Jon Turney [this message]
2022-10-30 18:35 ` Eliot Moss
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=831ebd6a-431e-9355-c8d6-8645e90e1180@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=moss@cs.umass.edu \
/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).