Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: Date: Wed, 23 Feb 2005 10:23:43 -0800 From: Matt Wilkie Reply-To: Matt Wilkie To: cygwin@cygwin.com Subject: Re: how to bring job to foreground? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: X-IsSubscribed: yes On Tue, 22 Feb 2005 18:17:26 -0800 (PST), Jeremy C. Reed 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/