X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 3 Jul 2009 12:44:23 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: popup consoles on Windows 7 Message-ID: <20090703104423.GA18746@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <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> <20090626145213 DOT GK30864 AT calimero DOT vinschen DOT de> <416096c60906270139y33e2888cq148430eebb744b71 AT mail DOT gmail DOT com> <20090628103010 DOT GT30864 AT calimero DOT vinschen DOT de> <20090702174425 DOT GC9839 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jul 3 10:18, Julio Costa wrote: > Let me rephrase that in three questions: > "What happens if we launch commands without a console created?" That's actually the same question as the next one, isn't it? > "What are the type of programs that really need that console?" Cygwin processes don't worry about the console. They use what they get as file descriptors and live with that. Native processes exist in two variations. Some of them just use the stdio handles like Cygwin processes. Some of them require to be run in a console becasue they use Console I/O functions directly. These applications will fail miserably in a Cygwin environment not attached to a console. Unfortunately there are quite a lot of them used for Windows system administration. At least that's as far as I rememeber this whole issue. I may have forgotten some aspect, but I'm fairly sure that we can drop the hidden console business as far as only Cygwin processes are affected. > "Is it possible to identify them prior to launch them?" Cygwin checks for a Cygwin application prior to execv it. Not a Cygwin application == may need a console. I have some testing code which only tries to create an invisible console if the application to execv is not a Cygwin application. It seems to work nicely. I'm just not sure if it's really *that* simple... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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