From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3) with ESMTP id QAA28846 for ; Thu, 25 Apr 1996 16:53:29 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id CAA28541; Thu, 25 Apr 1996 02:33:44 -0400 (EDT) Resent-Date: Thu, 25 Apr 1996 02:33:44 -0400 (EDT) Message-Id: Date: Thu, 25 Apr 96 08:34 MET DST From: wischnow@informatik.hu-berlin.de (Sven Wischnowsky) To: zsh-workers@math.gatech.edu In-reply-to: Richard Coleman's message of Thu, 25 Apr 1996 01:50:31 -0400 Subject: Re: where is this used? Resent-Message-ID: <"Za7y82.0.tz6.8pnVn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/953 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Richard Coleman wrote: > > The field `other' in the structure `job' appears to > only be set in execpline() and never used. Does anyone > know what this is for? > Once upon a time... when I was fiddling with the execution code I used this field. It was used for stopping pipelines with loops (and other shell-internal things) at the end. For doing that the current shell forked and used the child to represent the end of the pipe. The other field of the job representing the stopped child held the job number of the `old' job (the one representing the head of the pipe), so that both of them could be made runnable. Since there have been lots of changes in the execution and signal code I no longer know if it is still needed (maybe the fact that it isn't used anymore is connected to the fact that several bugs -- like the infamous never-^C-less-bug -- have reappeared). Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de