Path: utzoo!telly!ddsw1!lll-winken!brutus.cs.uiuc.edu!usc!snorkelwacker!apple!claris!sts!sts!roy
From: roy@sts.sts.COM
Newsgroups: gnu.bash.bug
Subject: background jobs in 1.04
Message-ID: <278200004@sts>
Date: 22 Nov 89 00:03:08 GMT
Lines: 16
Nf-ID: #N:sts:278200004:000:676
Nf-From: sts.sts.COM!roy    Nov 21 15:33:00 1989


I'm running Bash 1.04, compiled with gcc v1.30 on a Sun3/60 with SunOS
4.0.  I've just noticed that, if you put some jobs in the background
and they've completed, it takes an execution of a non-builtin command
(i.e. not the 'jobs' command) to make the shell realize that the jobs
are actually complete.  I don't see any reason why a builtin command
shouldn't do this.  The C shell will even notify you of job completion
after you've typed a carriage return.

Also, the C shell has a variable called 'notify', which when set, will
asynchronously notify you that your background job is finished.  How
about if Bash had this too?


Roy Bixler
roy@sts.COM -or- ames!claris!sts!roy