This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: run-1.1.11-1
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 Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple