🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.bash.bug
Article #772

Re: background jobs in 1.04

#772
From: Bill Trost
Date: Thu, 23 Nov 1989 00:52
16 lines
1087 bytes
Roy Bixler <roy@sts.com> writes:
"... 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?"

Seconded.  Waiting for jobs to complete has been rather bizarre in
bash, especially since the most natural way to see if a job is done is
by typing "jobs", and the command doesn't give correct information.
It would seem that the best place to see if jobs have been completed
would be right before the potential execution of the PROMPT_COMMAND.
--
--
Technical Details
Message-ID: <13611@reed.UUCP>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ctrsol!emory!ogccse!reed!trost
References: <278200004@sts>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ctrsol!emory!ogccse!reed!trost
From: trost@reed.bitnet (Bill Trost)
Newsgroups: gnu.bash.bug
Subject: Re: background jobs in 1.04
Message-ID: <13611@reed.UUCP>
Date: 23 Nov 89 00:52:39 GMT
References: <278200004@sts>
Sender: news@reed.UUCP
Lines: 16