From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23838 invoked from network); 5 Jul 2000 06:40:00 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 5 Jul 2000 06:40:00 -0000 Received: (qmail 1678 invoked by alias); 5 Jul 2000 06:39:45 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12169 Received: (qmail 1670 invoked from network); 5 Jul 2000 06:39:44 -0000 Date: Wed, 5 Jul 2000 08:39:38 +0200 (MET DST) Message-Id: <200007050639.IAA10663@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Tue, 4 Jul 2000 15:58:25 +0000 Subject: Re: PATCH: compdump (Re: Test hanger disappeared, but ...) Bart Schaefer wrote: > ... > > We seem to be running into a lot of things that cause zsh to abort all > the way back to top level. Do other shells give up so thoroughly in > these situations? That's interesting... For example, with while true; do echo > unwritable; sleep 1; done zsh stops after the first attempt. bash and ksh don't stop and the /bin/sh here stops after the first attempt, too. With while true; do echo $(for); sleep 1; done zsh stops (and prints two error messages!), bash does not stop, but ksh and /bin/sh do. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de