X-Spam-Check-By: sourceware.org Date: Thu, 18 May 2006 09:03:10 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [RFA] patch for run.exe -- ATTN: ago Message-ID: <20060518130310.GA10214@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <446C1803 DOT 2050901 AT cwilson DOT fastmail DOT fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <446C1803.2050901@cwilson.fastmail.fm> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Thu, May 18, 2006 at 02:45:23AM -0400, Charles Wilson wrote: >As detailed here: >http://cygwin.com/ml/cygwin/2006-05/msg00471.html > >run.exe currently launches clients without any stdio handles and without >any console at all. That's over-ambitious: what run REALLY should do is >launch the client with a *hidden* console and *working* stdio handles. > >Run is a console-hider, not a daemonizer -- and some apps (like, err, >rxvt-unicode), even tho they are GUIs, don't behave well when launched >without working stdio (even if those handles point to an invisible >console, and really shouldn't be used by the app anyway!) > >The attached patch adapts code from cygwin's fhandler_init, using >NT/2K/XP-only APIs to enable AllocConsole() to initialize the stdio >handles *without* that console ever becoming visible, not even for a >brief flash. Because these APIs are only available on some of the >supported OSes, I use LoadLibrary/GetProcAddress and function pointers, >so that on the older OSes the behavior should be unchanged from 1.1.9-1. Hopefully the run code is GPLed... cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/