Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
From:	Thorsten Kampe <thorsten AT thorstenkampe DOT de>
Subject:	Re: Ctrl-Z fails to suspend Windows programs
Date:	Thu, 17 Jun 2004 23:31:10 +0200
Lines:	42
Message-ID:	<h4o4z9lf4esc$.dlg@thorstenkampe.de>
References:	<87ekogc0uq DOT fsf AT eu DOT citrix DOT com> <Pine DOT LNX DOT 4 DOT 58 DOT 0406171259170 DOT 30937 AT ming DOT fruitbat DOT org>
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	isi-dial-142-158.isionline-dialin.de
User-Agent:	40tude_Dialog/2.0.12.1de

* Peter A. Castro (2004-06-17 22:13 +0100)
> On Tue, 15 Jun 2004, John Cooper wrote:
>>  > 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.
> 
> Hi John,
>   I'm the maintainer for zsh on Cygwin.
> 
>> Yes, you're right, the old "native" zsh option was specifically to do with GUI
>> apps rather than "Windows" apps per se - here's the doc to for enabling the
>> option (it was off by default):
>>
>>   winntwaitforguiapps: When set, makes the shell wait for win32 GUI apps to
>>   terminate instead of spawning them asynchronously.
>>
>>  > I don't think there's a reliable enough mechanism by which a shell could
>>  > detect one case from the other.
>>
>> Below is the code it used to determine if a program is a GUI program or not. I
>> don't know how well it works under all conditions; however it did work fine for
>> me.
>>
>> Even if not perfectly reliable, could something like this be added but disabled
>> by default?  I for one would find it useful.
> 
> I guess I don't really have much of a problem with adding such a feature,
> provided it's something that many users really want.  I can see some
> merit to it, but is it really that much work to type '&' after the
> command to run it in the background?

Why should Cygwin zsh have such a feature and make a difference
between a GUI and a non GUI application? When you invoke a non GUI
application, you won't return to the prompt unless the application has
finished. Same with zsh under Linux. If you start a GUI without a "&"
you don't get a prompt.

And you still can [Ctrl]+[C] the GUI app which you couldn't when it
was run in the background.

Thorsten


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

- Raw text -