From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 942 invoked from network); 10 Mar 1999 09:11:51 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 10 Mar 1999 09:11:51 -0000 Received: (qmail 24897 invoked by alias); 10 Mar 1999 09:11:06 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5725 Received: (qmail 24845 invoked from network); 10 Mar 1999 09:10:56 -0000 Message-Id: <9903100853.AA52035@ibmth.df.unipi.it> To: DEW16@daimlerchrysler.com, zsh-workers@math.gatech.edu Subject: Re: Signal-handling problem In-Reply-To: "DEW16@daimlerchrysler.com"'s message of "Tue, 09 Mar 1999 14:17:15 NFT." <0525672F.0069A984.00@lngodd02.notes.chrysler.com> Date: Wed, 10 Mar 1999 09:53:56 +0100 From: Peter Stephenson DEW16@daimlerchrysler.com wrote: > Okay, so I *LOVE* zsh, but I seem to have a small problem. For some reason, > it > doesn't know how to handle signals. The test for finding the signal names has obviously failed on your OS, so the array is far too short and when an unknown signal comes the shell looks for something which isn't there. You didn't say which version of zsh you have, but this mechanism has changed recently. The latest attempt is in http://www.ifh.de/~pws/computing/zsh-3.1.5-pws-11.tar.gz , but there is a relevant patch which has just appeared in zsh-workers message 5724, currently available at http://www.zsh.org/mla/workers/1999/msg00768.html (there's a better way of locating it by number but I couldn't get it to work). If that still doesn't work, it will need someone to look at what Src/signames1.awk and Src/signames2.awk are doing with this compiler and OS. -- Peter Stephenson Tel: +39 050 844536 WWW: http://www.ifh.de/~pws/ Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy