X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6409B3858CDA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1697876730;
	bh=LEeU2ux+smXrKsSVXBL12mX7l6zTwFu7r3QOCgjXHXg=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=uh1uq7oF92e/RHL2UKGy/o8VLBGBqgBA9dLeziQ1JlxbMb5/pYvAxUPsDCXwXmiI8
	 xuFqQlzIEhGuZGP2L5hQs3d1WDRXSk5eYRXOOp1OBP1jY9q9vO4qM7dyaupZm5UxCL
	 ZGjB4rb4DB212BgUsDq0RUaE+KqODTv3ob/lEEGo=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2151D3858D35
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 2151D3858D35
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1697876709; cv=none;
 b=g0iaqxcbp7H+6ZFbDB/GfELyeEvgWA/Y+QqXW4e/2Xquw0uVmQqoH6P+oeJU9jg48bXPGEIVjKDQi5kemUWoEitq4b3xSmfzI9yNKxRr1RqeiqDBatud1xNlQBZ0GD3WiIlui9yDed+fiWcXqsbB3urHfvW0cZK+PgaANCZStvk=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1697876709; c=relaxed/simple;
 bh=G8Q0vV4C60HVXk41b1DqOTTOLeXtsE/pQsNPvLCyPnQ=;
 h=Message-ID:Date:MIME-Version:Subject:To:From;
 b=Vq9CjUgFMcLMB/XrH6lGKcjGdP0qCDvnonuNsIriRTaMRyzaNDPrQSXPpf5aAgwDUX+N6ok4zNuZ9aSY2n67rg15U4tEQ9m4dIRaUUurxEoW6OD0kQtIO72d23SopEM29hqa+DGB11Tyc2bprtxl/RHcX/ChPI93bmKQLVbljUc=
ARC-Authentication-Results: i=1; server2.sourceware.org
X-Virus-Scanned: Debian amavisd-new at smtp01.aussiebb.com.au
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 SPF_HELO_NONE, SPF_SOFTFAIL,
 TXREP autolearn=no autolearn_force=no version=3.4.6
Message-ID: <56c54a91-7f9a-4eec-a1e4-1bf4429ebec4@shaddybaddah.name>
Date: Sat, 21 Oct 2023 19:24:40 +1100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Cygwin/X - *bizarre discovery* doorknock like behaviour for new
 windows
Content-Language: en-GB
To: cygwin AT cygwin DOT com
References: <a22bf269-ad22-4bdc-814f-bf5594e845e8 AT shaddybaddah DOT name>
 <3ee1ac1f-e828-4407-9826-74d3e70e77ad AT shaddybaddah DOT name>
In-Reply-To: <3ee1ac1f-e828-4407-9826-74d3e70e77ad@shaddybaddah.name>
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Shaddy Baddah via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Shaddy Baddah <lithium-cygwin AT shaddybaddah DOT name>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Hi,

On 20/10/2023 12:40 pm, Shaddy Baddah via Cygwin wrote:
> 
> 
> On 20/10/2023 11:50 am, Shaddy Baddah via Cygwin wrote:
>> What I am seeing is that for Cygwin/X, in multi-window mode (and it
>> just occurred to me it would be helpful to check the behaviour in
>> rooted(? manual page terminology) mode. I'll follow-up on this)...
>> in multi-window mode (Xwin -multiwindow), when I try to open an X window
>> for any given app, it is not displayed on the first run.
> 
> For completeness, rooted mode does not have this issue.
> 
> Also, a further note, once reproduced, further reproductions may require
> exiting XWin, and restarting it.

I've found a bizarre, and to me, a hilarious, reason for this behaviour.

So my assertion that it happens once per app is wrong. It happens only
on the very first run of an X11 app on a newly started Xwin server. I
guess I noticed this when I ran different X11 apps as the first run app
against the Xwin server, and drew that longbow. Apologies for any
confusion. But it still happens that very first time.

*And* the app is actually displayed. Bizarely though, it is trapped
within the confines of the ConEmu (https://conemu.github.io/) command
session Xwin was started under. So if that ConEmu session is not at
the front of the visible stack, you have no idea the app has been
displayed/rendered.

I haven't looked, but I speculate ConEmu, which is feature rich, has
some feature that makes it act as a "rooted" X window? It feels like a
reach though... the other theory is that something with it's DLL
injection perhaps. I'll look at that separate from Cygwin/X though.

I have tried using regular Windows command prompt, and this doesn't
happen. Nor with the Windows (Metro) Terminal app.

Again, sorry for any confusion this has caused.

-- 
Regards,
Shaddy

-- 
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