zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: SUGGESTION: kill -l could show numbers, too (+CLD vs CHLD)
Date: Thu, 18 Nov 2004 17:22:56 +0000	[thread overview]
Message-ID: <6451.1100798576@csr.com> (raw)
In-Reply-To: <20041118163901.GD4511@sc>

Stephane Chazelas wrote:
> Why SIGCLD and not SIGCHLD for zsh?

It's an artefact of this sort of thing in header files:

#define	SIGCLD		SIGCHLD	/* Same as SIGCHLD (System V).  */
#define	SIGCHLD		17	/* Child status has changed (POSIX).  */

We pick the first one, assuming that's to be preferred.

The following explicitly prefers SIGCHLD.  Any other multiple signals
can be handled similarly.  I'm not sure about SIGPOLL.

Maybe we should think about mapping alternatives so that both kill -CLD
and kill -CHLD work.

Index: Src/signames2.awk
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/signames2.awk,v
retrieving revision 1.3
diff -u -r1.3 signames2.awk
--- Src/signames2.awk	12 Mar 2004 09:59:24 -0000	1.3
+++ Src/signames2.awk	18 Nov 2004 17:15:22 -0000
@@ -12,6 +12,7 @@
     split(sigtail, tmp)
     signam = substr(tmp[1], 4, 20)
     signum = tmp[2]
+    if (signam == "CHLD" && sig[signum] == "CLD")  sig[signum] = ""
     if (sig[signum] == "") {
 	sig[signum] = signam
 	if (0 + max < 0 + signum && signum < 60)

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  reply	other threads:[~2004-11-18 17:24 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   ` SUGGESTION: kill -l could show numbers, too (+CLD vs CHLD) Stephane Chazelas
2004-11-18 17:22     ` Peter Stephenson [this message]
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=6451.1100798576@csr.com \
    --to=pws@csr.com \
    --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).