From: Richard Coleman <coleman@math.gatech.edu>
To: wischnow@informatik.hu-berlin.de (Sven Wischnowsky)
Cc: zsh-workers@math.gatech.edu
Subject: Re: where is this used?
Date: Thu, 25 Apr 1996 02:48:01 -0400 [thread overview]
Message-ID: <199604250648.CAA08013@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Thu, 25 Apr 1996 08:34:00 +0700." <m0uCKdI-0000ZnC@enterprise.informatik.hu-berlin.de>
> > 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).
I just went through some of the older distributions looking into this.
It appears the `other' field first appeared in zsh-2.5.02. But in all
distributions it was only set and never used. So it's removal is probably
not the cause of our problem with signals.
rc
next prev parent reply other threads:[~1996-04-25 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-25 6:34 Sven Wischnowsky
1996-04-25 6:48 ` Richard Coleman [this message]
1996-04-25 13:03 ` cd =5 changed semantics? Andreas Koenig
1996-04-25 14:14 ` Zefram
-- strict thread matches above, loose matches on Subject: below --
1996-04-25 5:50 where is this used? Richard Coleman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199604250648.CAA08013@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).