This is the mail archive of the
mailing list for the Cygwin project.
Re: how to bring job to foreground?
- From: Matt Wilkie <maphew at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 23 Feb 2005 10:23:43 -0800
- Subject: Re: how to bring job to foreground?
- References: <firstname.lastname@example.org> <Pine.LNX.email@example.com>
- Reply-to: Matt Wilkie <maphew at gmail dot com>
On Tue, 22 Feb 2005 18:17:26 -0800 (PST), Jeremy C. Reed
> 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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html