Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PRINT_EXIT_VALUE: Suppress for if/while conditions
- X-seq: zsh-workers 36164
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: PRINT_EXIT_VALUE: Suppress for if/while conditions
- Date: Fri, 14 Aug 2015 09:19:45 +0100
- In-reply-to: <20150813232020.GF1998@tarsus.local2>
- 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
- Organization: Samsung Cambridge Solution Centre
- References: <20150731231225.GB2054@tarsus.local2> <20150813093238.046a1b08@pwslap01u.europe.root.pri> <20150813232020.GF1998@tarsus.local2>
On Thu, 13 Aug 2015 23:20:20 +0000
Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> I have no problem with ruling out the jobs/bg/fg callsites, as you
> propose. However, checking (synch == 1) would also mean the value of
> PRINTEXITVALUE is entirely ignored when printjob() is called
> asynchronously. I can see that that is fine for jobs that don't have
> STAT_NOPRINT set.¹ Is it also correct to ignore PRINTEXITVALUE in the
> case (synch == 0 && (jn->stat & STAT_NOPRINT))?
My point is really that you don't want to *modify* the code unless synch
== 1. So sync == anything else should continue to do just what it does
at the moment, but if synch == 1 you can apply your extra check. That
seems likely to do the nearest to what everybody wants.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author