X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 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: <20090626133618.GA14187@calimero.vinschen.de>
References: <416096c60904210835jd93a1b8w742bb8ebe0802c9c AT mail DOT gmail DOT com>  	<20090508090737 DOT GA15230 AT calimero DOT vinschen DOT de> <416096c60905131134l21aa53dqe7c3f99130dddb4e AT mail DOT gmail DOT com>  	<20090626083640 DOT GF30864 AT calimero DOT vinschen DOT de> <416096c60906260239r5bdaf60bw6a9febe885726f55 AT mail DOT gmail DOT com>  	<20090626102313 DOT GA12963 AT calimero DOT vinschen DOT de> <416096c60906260503o52ae73ben1140bbbd2db993bb AT mail DOT gmail DOT com>  	<20090626121215 DOT GJ30864 AT calimero DOT vinschen DOT de> <416096c60906260541t56687113p9c940d4251f68405 AT mail DOT gmail DOT com>  	<20090626133618 DOT GA14187 AT calimero DOT vinschen DOT de>
From: Julio Costa <costaju AT gmail DOT com>
Date: Fri, 26 Jun 2009 15:08:44 +0100
Message-ID: <af075b00906260708h674121f3s63fdc79af5675a44@mail.gmail.com>
Subject: Re: popup consoles on Windows 7
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

Hi,

On Fri, Jun 26, 2009 at 14:36, Corinna Vinschen wrote:
> On Jun 26 13:41, Andy Koppe wrote:
>> 2009/6/26 Corinna Vinschen:
>> >> Forgot to say: the occurances of this could at least be reduced by
>> >> trying AttachConsole to get a hold on the parent process' console, if
>> >> any. When I attempted that in MinTTY, though, I couldn't make it work.
>> >
>> > Yes, I thought of trying AttachConsole first. =C2=A0It's a band-aid si=
nce
>> > it will of course not work if there's just no parent console
>>
>> That can be dealt with, because AttachConsole reports back whether it
>> did manage to attach, so if it doesn't, one can then call AllocConsole
>> and ShowWindowAsync.
>
> Yes, I'm aware how this would work. =C2=A0What I mean is, it's *still* a
> band-aid since in case of a fail to attach, you still have to alloc
> a console and you're back to the original problem. =C2=A0What we could do
> using that technique is to minimize the number of console windows.
> But it doesn't help to avoid them entirely. =C2=A0You have still cluttered
> your desktop, or rather, your taskbar with console windows.
>

I've been following this discussion, crossing fingers to someone came
to some conclusion, as this is the biggest show-stopper for Cygwin in
several months.

I've not access to a Win 7, but I would like at least to drop some
ideas to someone with more insight comment on and (hopefully) come to
a solution.

1) If we make a service (let's call it cygconsole, or include it in
cygserver, whatever), with no desktop interaction, whose only purpose
is to AllocConsole()...
1.a) do that console gets created?
1.b) Is it invisible?

2) IF the two answers are true, then
2.a) Do an arbitary process can do an attachconsole to the PID of that serv=
ice?

IF it is also an YES, we have a framework for an
workaround/alternative implementation! Cool?

(crossing fingers)
___________
Julio Costa

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