X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20090705001152.GA2510@ednor.casa.cgf.cx>
References: <af075b00906260708h674121f3s63fdc79af5675a44 AT mail DOT gmail DOT com> 	 <416096c60906270139y33e2888cq148430eebb744b71 AT mail DOT gmail DOT com> 	 <20090628103010 DOT GT30864 AT calimero DOT vinschen DOT de> 	 <af075b00907020941i666bed61vc450315c662b757a AT mail DOT gmail DOT com> 	 <20090702174425 DOT GC9839 AT ednor DOT casa DOT cgf DOT cx> 	 <af075b00907030218p54b606ds813e824422de04fa AT mail DOT gmail DOT com> 	 <20090703104423 DOT GA18746 AT calimero DOT vinschen DOT de> 	 <20090703150212 DOT GA26858 AT ednor DOT casa DOT cgf DOT cx> 	 <20090704161431 DOT GB11034 AT ednor DOT casa DOT cgf DOT cx> 	 <20090705001152 DOT GA2510 AT ednor DOT casa DOT cgf DOT cx>
Date: Sun, 5 Jul 2009 10:33:47 +0100
Message-ID: <416096c60907050233q344d37cds41859c611c7ab660@mail.gmail.com>
Subject: Re: popup consoles on Windows 7
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

2009/7/5 Christopher Faylor:
> I've checked in a workaround for the problem:
>
> http://cygwin.com/ml/cygwin-cvs/2009-q3/msg00010.html
>
> I checked this by removing the Windows 7 code from mintty and rebuilding
> it. =C2=A0With the currently released version of Cygwin 1.7.0-50 this cau=
ses
> a windows console to be displayed on the screen along with the expected
> mintty window. =C2=A0With the 20090703 snapshot, which includes Corinna's
> workaround, I got a flashing console. =C2=A0With the code in CVS I got the
> expected behavior of no console flash.

Works for me on Windows 7 RC 64-bit. Thanks you very very much, looks
so much better without those subliminal consoles. And Xwin is fine
too. What was the big idea?

It doesn't appear to suffer from MinTTY issue 83 either. ("MinTTY
hangs the console/shell it launched from on Win7-64",
http://code.google.com/p/mintty/issues/detail?id=3D83). That issue was
why I'd removed AttachConsole calls from MinTTY, but perhaps MS had
actually fixed whatever caused it in the release candidate.

Now what's the right way to check for this workaround being present in
the Cygwin DLL, so that MinTTY can skip its workaround depending on
that? Should I parse version string from /proc/version? (I intend to
throw out MinTTY's workaround altogether when going 1.7-only, but for
the moment it needs to stay.)


> As I type this I realize that I didn't really confirm that the new
> invisible console code has the desired effect in mintty.  It is supposed
> to make some (native?) apps work better.

No, its main purpose is to stop console subsystem applications from
popping up their own console. This includes most Cygwin programs
(which I think is wrong).


>=C2=A0I thought that one of the apps
> was the "net" command and I don't have any problems running it but does
> anyone remember a specific program (maybe even a cygwin program?) which
> required the existence of a console to work correctly?

I think this concerns apps that directly use the low-level console
API, but I don't know of any specific examples either. I've seen 'net'
mentioned too, so perhaps it does invoke a low-level API function or
two, but without significantly depending on their effects.


> If you want to try a snapshot, make sure that you grab the new helper
> app "cygwin-console-helper.exe" and put it in /bin. =C2=A0Without this,
> you'll still see the same flashes as the 20090703 snapshot.

I see the code for invoking it, but I don't fully understand it: how
come the helper process doesn't show up in task manager (which is
great, btw)?

A very minor issue in fhandler_console.cc: one of the comments says
"workstation" when it means "window station".


> I keep saying that I want to fix this and I recently found some public
> domain code which purports to allow using consoles as "pipes".  I hope
> I'll have time to look into adding this to Cygwin after 1.7 is released.

Oh, interesting, could you post a link to it?

Thanks again,
Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple