Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Backgroun job return code
- X-seq: zsh-users 14804
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users <zsh-users@xxxxxxx>
- Subject: Re: Backgroun job return code
- Date: Sat, 06 Feb 2010 18:58:03 -0800
- In-reply-to: <787bbe1c1002060409i7363148au8e8c8fc56dc8c63@xxxxxxxxxxxxxx>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <787bbe1c1002050410k6355e368hb6255bc33754dddf@xxxxxxxxxxxxxx> <1265408376-sup-2466@nixos> <787bbe1c1002060409i7363148au8e8c8fc56dc8c63@xxxxxxxxxxxxxx>
On Feb 6, 1:09pm, Slawek Zak wrote:
}
} Threading is really not necessary to get this. One idea would be
} calling the TRAPEXIT function for *all* jobs, not only the foreground
No, TRAPEXIT refers to the exit of the shell itself, or of a shell
function, not of a job (not even the foreground job).
What you really want is for TRAPCHLD to have access to the exit status
(and possibly other job data) of the child that caused it to be called.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author