Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Dave Korn" <dk@artimi.com>
To: "'John Cooper'" <John.Cooper@eu.citrix.com>, <cygwin@cygwin.com>
Subject: RE: Ctrl-Z fails to suspend Windows programs
Date: Tue, 15 Jun 2004 15:40:11 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <87isdsc3xl.fsf@eu.citrix.com>
Message-ID: <NUTMEGY7PeGbPn6U9Be0000038b@NUTMEG.CAM.ARTIMI.COM>

> -----Original Message-----
> From: cygwin-owner On Behalf Of John Cooper
> Sent: 15 June 2004 15:05
> To: cygwin
> Subject: RE: Ctrl-Z fails to suspend Windows programs
> 
> The old native (non-cygwin) port of zsh would somehow detect 
> if it was about to
> exec a Windows app, and run it as a background process, thus 
> returning a zsh
> prompt immediately.  Could something like this be added to 
> cygwin bash/zsh?

  AFAICS the ability is already there.  Just enter "windows_app.exe &" at a
bash shell.

> This was very useful.  With the cygwin zsh, I often find 
> myself invoking a
> Windows app and not being able to get back to the shell 
> window without first
> terminating the Windows app.

Well, the same goes if you run a cygwin app: you don't get the prompt back
until it exits.
 
The point is that it's not about cygwin-vs-windoze apps.  It's about
apps-that-use-console-stdin-and-stdout vs. apps-that-display-a-gui; those
that show a gui could usefully be detached, but those that read their input
from stdin will break if the shell detaches them.  I don't think there's a
reliable enough mechanism by which a shell could detect one case from the
other.

Try starting insight (gui version of gdb) from the bash prompt.  You also
won't get a shell back until it exits.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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