From: Martijn Dekker <martijn@inlv.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: exit status 0 after SIGINT
Date: Mon, 25 Sep 2017 13:50:15 +0100 [thread overview]
Message-ID: <2f98bd49-1439-2bd9-c7b2-7d05ac8678fc@inlv.org> (raw)
zsh in interactive mode sets the exit status to 0 after sending itself
SIGINT using the 'kill' command. I'd expect 130 (= 2 + 128).
Interestingly enough, pressing Ctrl+C does set the exit status to 130.
% [presses Ctrl+C]
% echo $?
130
% kill -s INT $$
$ echo $?
0
- Martijn
next reply other threads:[~2017-09-25 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170925125104epcas5p3948e0702e32903ad3a09070937edbb54@epcas5p3.samsung.com>
2017-09-25 12:50 ` Martijn Dekker [this message]
2017-09-25 13:57 ` Peter Stephenson
2017-09-26 10:57 ` Martijn Dekker
2017-09-26 17:49 ` Bart Schaefer
2017-09-27 8:35 ` Peter Stephenson
2017-09-27 19:59 ` Bart Schaefer
2017-09-26 18:15 ` Peter Stephenson
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=2f98bd49-1439-2bd9-c7b2-7d05ac8678fc@inlv.org \
--to=martijn@inlv.org \
--cc=zsh-workers@zsh.org \
/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).