From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-41765-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 22520 invoked by alias); 26 Sep 2017 10:57:40 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 41765
Received: (qmail 13865 invoked by uid 1010); 26 Sep 2017 10:57:40 -0000
X-Qmail-Scanner-Diagnostics: from kahlil.inlv.org by f.primenet.com.au (envelope-from <martijn@inlv.org>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(37.59.109.123):SA:0(-1.9/5.0):. 
 Processed in 1.661582 secs); 26 Sep 2017 10:57:40 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD
	autolearn=ham autolearn_force=no version=3.4.1
X-Envelope-From: martijn@inlv.org
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Subject: Re: exit status 0 after SIGINT
To: Zsh hackers list <zsh-workers@zsh.org>
References: <CGME20170925125104epcas5p3948e0702e32903ad3a09070937edbb54@epcas5p3.samsung.com>
 <2f98bd49-1439-2bd9-c7b2-7d05ac8678fc@inlv.org>
 <20170925145717.13849173@pwslap01u.europe.root.pri>
From: Martijn Dekker <martijn@inlv.org>
Message-ID: <757d2c4c-fb9f-d168-c70a-08560677a181@inlv.org>
Date: Tue, 26 Sep 2017 11:57:33 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
 Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <20170925145717.13849173@pwslap01u.europe.root.pri>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit

Op 25-09-17 om 14:57 schreef Peter Stephenson:
> We ignore interrupts that happened in bulltins, in this case the "kill"
> that just got interrupted.  This looks pretty clearly wrong.
> 
> One minimal fix is to keep the current lastval if there's an interrupt
> flagged.  Alternatively, we could keep the builtin status if it was
> non-zero.
> 
> I doubt we're going to track down side effects without trying it out.

An oddity remains:

% kill -s INT $$ || echo oops
% echo $?
1
% kill -s INT $$ && echo oops
% echo $?
130

Both should be 130.

This is the same when using external 'kill' (e.g. after 'disable kill').

Thanks,

- M.