From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11036 invoked from network); 10 Mar 1999 23:42:18 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 10 Mar 1999 23:42:17 -0000 Received: (qmail 27552 invoked by alias); 10 Mar 1999 23:41:46 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5745 Received: (qmail 27533 invoked from network); 10 Mar 1999 23:41:44 -0000 From: DEW16@daimlerchrysler.com X-Lotus-FromDomain: CHRYSLER To: zsh-workers@sunsite.auc.dk Message-ID: <85256730.00821433.00@lngodd02.notes.chrysler.com> Date: Wed, 10 Mar 1999 18:43:59 -0500 Subject: Re: Signal-handling problem Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline 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. Peter Stephenson wrote: >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 Say, thank you and everyone else for the tips. You were precisely correct. I'm using zsh 3.0.5, and I discovered that, for some reason, my version of gawk (3.0.3) wasn't working correctly when invoked to create signals.h. I was able to sidestep this by editing the Makefile in the Src directory so that AWK = nawk (instead of gawk) and recompiling. The output from 'kill -l' looks reasonable now (i.e., it's not empty!) and the signal-handling seems to work just fine... Thanks again, -Dave