Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Using "source" in a function breaks job control

X-seq: zsh-workers 34951
From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
To: "Zsh Hackers' List" <zsh-workers@xxxxxxx>
Subject: Re: Using "source" in a function breaks job control
Date: Thu, 23 Apr 2015 21:13:31 +0100
In-reply-to: <150422215539.ZM14251@torch.brasslantern.com>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <5537E450.9060205@thequod.de> <20150422222627.1f6154e9@ntlworld.com> <150422215539.ZM14251@torch.brasslantern.com>

On Wed, 22 Apr 2015 21:55:39 -0700
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> It has something to do with tracking the job table.

Looks like we lost STAT_SUPERJOB in the flags of the job that got
created when we forked.  In the bad case the STAT_ flags are
SUBLEADER|CURSH|INUSE|LOCKED and in the good case there is also
SUPERJOB.  The SUBLEADER in the bad case means that the logic was
probably on roughly the right lines, though that's not a great surprise
since we can see the forked subshell is there.  SUPERJOB can only get
added at one point in execpline(), although it can also be removed but
in that case the job should get WASSUPER which doesn't get removed until
the job is cleared.  So the differences in execpline(), which I never
understood, might be informative.

pws

Follow-Ups:
- Re: Using "source" in a function breaks job control
  - From: Bart Schaefer

References:
- Using "source" in a function breaks job control
  - From: Daniel Hahler
- Re: Using "source" in a function breaks job control
  - From: Peter Stephenson
- Re: Using "source" in a function breaks job control
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author