Message-ID: <4A86CA3F.9010204@cwilson.fastmail.fm>
Date: Sat, 15 Aug 2009 10:46:23 -0400
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: run-1.1.11-1
References: <20090814144442.GF32408@calimero.vinschen.de> <20090814151921.GA28983@ednor.casa.cgf.cx> <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>
In-Reply-To: <20090815085738.GB13648@calimero.vinschen.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Corinna Vinschen wrote:
> On Aug 14 17:39, Ken Brown wrote:
>> On 8/14/2009 2:48 PM, Corinna Vinschen wrote:
>>>> Given that the X server shortcut is just a `run /usr/bin/startxwin.bat',
>>>> is it possible that the new incarnation doesn't start cmd correctly?
>>> I built with -DDEBUG and it appears that startxwin.bat runs fine,
>>> but the "run within run" inside of startxwin.bat
>>>
>>>   %RUN% XWin -multiwindow -clipboard -silent-dup-error
>>>
>>> fails silently.
>> I can confirm that the shortcut to start the X server doesn't work on my  
>> XP system with the patched run.  But my shortcut for starting emacs  
>> (http://cygwin.com/ml/cygwin/2009-08/msg00379.html), which has a very  
>> similar run within run, works fine.
> 
> 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?

--
Chuck

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