From: Stephane Chazelas <Stephane_Chazelas@yahoo.fr>
To: zsh-workers@sunsite.dk
Subject: Re: SUGGESTION: kill -l could show numbers, too (+CLD vs CHLD)
Date: Thu, 18 Nov 2004 16:39:01 +0000 [thread overview]
Message-ID: <20041118163901.GD4511@sc> (raw)
In-Reply-To: <20310.1100793917@csr.com>
On Thu, Nov 18, 2004 at 04:05:17PM +0000, Peter Stephenson wrote:
> Christian =?iso-8859-1?Q?H=F6ltje?= wrote:
> > I have a suggestion for the kill builtin:
> >
> > It would be nice if when you did '-l' to show the list of signal
> > that it show the signal number.
>
> Not quite as convenient, but try this function:
>
> kill-l() {
> for i in {1..$#signals}; do
> print $((i-1))\) SIG$signals[$i]
> done | pr -t5
> }
[...]
Or, to avoid "pr":
kill-l () {
local -a s
for i in {1..$#signals}
do
s[i]="$((i-1))) SIG$signals[$i]"
done
print -C5 $s
}
BTW, I noted some discrepancies on the result of kill -l between
various shells and /bin/kill on that Linux-i386:
bash bin csh dash ksh pdksh zsh
ABRT ABRT ABRT ABRT IOT ABRT ABRT
STKFLT STKFLT 16 SIG16 STKFLT STKFLT
CHLD CHLD CHLD CHLD CHLD CHLD CLD
IO POLL POLL IO POLL IO POLL
SYS SYS SYS SYS SYS UNUSED SYS
Why SIGCLD and not SIGCHLD for zsh?
SUSv3 (POSIX) seems to require SIGCHLD
http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html
http://www.opengroup.org/onlinepubs/009695399/utilities/trap.html
--
Stéphane
next prev parent reply other threads:[~2004-11-18 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 14:52 SUGGESTION: kill -l could show numbers, too Christian Höltje
2004-11-18 16:05 ` Peter Stephenson
2004-11-18 16:12 ` Dan Nelson
2004-11-18 16:33 ` Bart Schaefer
2004-11-18 16:50 ` Stephane Chazelas
2004-11-18 16:39 ` Stephane Chazelas [this message]
2004-11-18 17:22 ` SUGGESTION: kill -l could show numbers, too (+CLD vs CHLD) Peter Stephenson
2004-11-19 9:59 ` Peter Stephenson
2004-11-19 15:34 ` Bart Schaefer
2004-11-19 16:02 ` Peter Stephenson
2004-11-20 19:29 ` 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=20041118163901.GD4511@sc \
--to=stephane_chazelas@yahoo.fr \
--cc=zsh-workers@sunsite.dk \
/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).