Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.mixmin.net!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!news.tele.dk!news.tele.dk!small.news.tele.dk!usenet.stanford.edu!not-for-mail From: Ian Jackson Newsgroups: gnu.bash.bug Subject: Re: Want way to run background processes with SIGINT unignored Date: Tue, 13 Oct 2015 15:58:44 +0100 Lines: 31 Approved: bug-bash@gnu.org Message-ID: References: <22040.2725.561993.552660@chiark.greenend.org.uk> <561951D3.30606@case.edu> <22042.26444.280754.417761@chiark.greenend.org.uk> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1444748403 26262 208.118.235.17 (13 Oct 2015 15:00:03 GMT) X-Complaints-To: action@cs.stanford.edu To: chet.ramey@case.edu, bug-bash@gnu.org Envelope-to: bug-bash@gnu.org In-Reply-To: <22042.26444.280754.417761@chiark.greenend.org.uk> X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:ba8:1e3:: X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:11648 Ian Jackson writes ("Re: Want way to run background processes with SIGINT unignored"): > Chet Ramey writes ("Re: Want way to run background processes with SIGINT unignored"): > > This is the behavior that any new option would toggle. Some name like > > `async_sig_ignore' or `async_sig_restore' would work. > > Thanks for your attention and your feedback; I'll get back to you with > a patch. This patch is nearly ready and I will send it shortly. While I was working on the docs aspect I noticed an infelicity in the documentation. It generally talk about the signal disposition that the shell `inherits from its parent'. For example: traps caught by the shell are reset to the values inherited from the shell's parent, and traps ignored by the shell are ignored But this is misleading. The values that the signals are reset to are those which the parent inherited _at shell invocation_ (ie, at exec). If the shell is a subshell (produced with `( )' perhaps), it may have inherited different settings from its _parent_ (ie, the main shell). I think this wording should be changed throughout to read `inherited at shell invocation'. Do you agree ? Would you welcome a patch along those lines ? Thanks, Ian.