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
Message-ID:	<c61d98af050223102325ac01b2@mail.gmail.com>
Date:	Wed, 23 Feb 2005 10:23:43 -0800
From:	Matt Wilkie <maphew AT gmail DOT com>
Reply-To:	Matt Wilkie <maphew AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: how to bring job to foreground?
In-Reply-To:	<Pine.LNX.4.43.0502221816040.12069-100000@pilchuck.reedmedia.net>
Mime-Version:	1.0
References:	<c61d98af05022215266e5bb20a AT mail DOT gmail DOT com> <Pine DOT LNX DOT 4 DOT 43 DOT 0502221816040 DOT 12069-100000 AT pilchuck DOT reedmedia DOT net>
X-IsSubscribed:	yes

On Tue, 22 Feb 2005 18:17:26 -0800 (PST), Jeremy C. Reed
<reed AT reedmedia DOT net> wrote:
> On Tue, 22 Feb 2005, Matt Wilkie wrote:
> 
> > thanks for your help Jeremy.
> 
> You are welcome.
> 
> > Although -SIGCONT didn't completely work in this circumstance I'm glad
> > of the knowledge. I've encountered similar situations before and knew
> > there had to be _some_ way of reactivating a process from another
> > console. It never occured to read up on 'kill' in this context, what I
> > was attempting was precisely the opposite after all. :)
> 
> The strange thing I noticed with my tests with bash is that it still said
> job was suspended when really it was running (after the kill -SIGCONT).

Yeah, that's what I get too. I guess suspending apps with ctrl-z
instead of & on windows is still chancy.

-- 
-matt

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