Date: Sun, 16 Aug 2009 11:24:54 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: run-1.1.11-1
Message-ID: <20090816092454.GL32408@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20090814152904.GG32408@calimero.vinschen.de> <20090814154349.GA10002@ednor.casa.cgf.cx> <20090814162049.GH32408@calimero.vinschen.de> <4A859A59.1040308@cwilson.fastmail.fm> <4A85A9F3.9090108@cwilson.fastmail.fm> <20090814184157.GI32408@calimero.vinschen.de> <20090814184849.GJ32408@calimero.vinschen.de> <4A85D99B.80101@cornell.edu> <20090815085738.GB13648@calimero.vinschen.de> <4A86CA3F.9010204@cwilson.fastmail.fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A86CA3F.9010204@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Aug 15 10:46, Charles Wilson wrote:
> Corinna Vinschen wrote:
> > Apparently `run XWin' doesn't work at all anymore, everything else seems
> > to work fine.  A shortcut starting XWin directly w/o run works fine as
> > well.  Is XWin allergic against the pipe redirection, maybe?
> 
> Hmm. I've been testing using the XMing xserver, just to avoid any
> possible complications on the client side; that's why I didn't notice
> the problem.
> 
> It seems that emacs.exe (and even emacs-X11,exe) are both console
> programs, while XWin.exe is a GUI program (that is, "objdump -p $prog |
> grep ^Subsystem" reports
> 
> Subsystem               00000002        (Windows GUI)
> 
> rather than
> 
> Subsystem               00000003        (Windows CUI)
> 
> So...food for thought.
> 
> 
> 
> Anyway, I thought about adding a cmdline switch to run, to allow the
> user to choose whether stdio handle redirection should happen.  But I'd
> really rather it were automatic.  Then I got to thinking, /IF/ the
> problem is GUI mode programs, then...maybe run can probe the PE header,
> determine if the target is already GUI, and if so...just launch it using
> exec (_spawn on MinGW)?
> 
> That way, all this mess is avoided -- really, the console-hiding
> property of "run" is kinda pointless for GUI progs; the only value it
> adds in that case is (a) -p setting the PATH, and (b) -wait.  So...just
> skip all the console-hiding stuff.
> 
> Do you think this idea is worth pursuing?

Sounds like a good idea to me.  I'm just wondering, is there really
no easy Win32 function to fetch this information, along the lines
of the GetBinaryType function?


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