From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: SIGTTOU old problem
Date: Mon, 28 Feb 2005 14:24:59 +0000 [thread overview]
Message-ID: <200502281424.j1SEOx2P012505@news01.csr.com> (raw)
In-Reply-To: <200502281413.j1SEDSP1011969@news01.csr.com>
Peter Stephenson wrote:
> By the way, this will fail if sh happens to be zsh since we don't strip
> the SIG from the signal name, which appears to be optional in other
> shells. (ksh and bash differ in whether the output shows the SIG or not.)
This is easy to fix.
Index: Doc/Zsh/builtins.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/builtins.yo,v
retrieving revision 1.74
diff -u -r1.74 builtins.yo
--- Doc/Zsh/builtins.yo 19 Jan 2005 13:04:09 -0000 1.74
+++ Doc/Zsh/builtins.yo 28 Feb 2005 14:21:20 -0000
@@ -1157,8 +1157,9 @@
item(tt(trap) [ var(arg) [ var(sig) ... ] ])(
var(arg) is a series of commands (usually quoted to protect it from
immediate evaluation by the shell) to be read and executed when the shell
-receives var(sig). Each var(sig) can be given as a number
-or as the name of a signal.
+receives var(sig). Each var(sig) can be given as a number,
+or as the name of a signal either with or without the string tt(SIG)
+in front.
If var(arg) is `tt(-)', then all traps var(sig) are reset to their
default values. If var(arg) is the empty string, then this signal
is ignored by the shell and by the commands it invokes.
Index: Src/jobs.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/jobs.c,v
retrieving revision 1.37
diff -u -r1.37 jobs.c
--- Src/jobs.c 14 Jan 2005 13:05:21 -0000 1.37
+++ Src/jobs.c 28 Feb 2005 14:21:20 -0000
@@ -1874,6 +1874,8 @@
while (*++argv) {
sig = zstrtol(*argv, &signame, 10);
if (signame == *argv) {
+ if (!strncmp(signame, "SIG", 3))
+ signame += 3;
for (sig = 1; sig <= SIGCOUNT; sig++)
if (!cstrpcmp(sigs + sig, &signame))
break;
@@ -1942,7 +1944,8 @@
} else
signame = *argv;
makeuppercase(&signame);
- if (!strncmp(signame, "SIG", 3)) signame+=3;
+ if (!strncmp(signame, "SIG", 3))
+ signame+=3;
/* check for signal matching specified name */
for (sig = 1; sig <= SIGCOUNT; sig++)
@@ -2032,6 +2035,9 @@
return x;
/* search for signal by name */
+ if (!strncmp(s, "SIG", 3))
+ s += 3;
+
for (i = 0; i < VSIGCOUNT; i++)
if (!strcmp(s, sigs[i]))
return i;
--
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.
**********************************************************************
next prev parent reply other threads:[~2005-02-28 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 13:41 Borzenkov Andrey
2005-02-28 14:13 ` Peter Stephenson
2005-02-28 14:24 ` Peter Stephenson [this message]
2005-02-28 14:29 ` Philippe Troin
2005-02-28 14:29 ` Re[2]: " Borzenkov Andrey
2005-02-28 15:23 ` Philippe Troin
2005-03-14 7:54 ` Philippe Troin
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=200502281424.j1SEOx2P012505@news01.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).