From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25035 invoked from network); 13 Mar 2000 17:09:05 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Mar 2000 17:09:05 -0000 Received: (qmail 7971 invoked by alias); 13 Mar 2000 17:08:58 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10122 Received: (qmail 7952 invoked from network); 13 Mar 2000 17:08:57 -0000 From: "Bart Schaefer" Message-Id: <1000313170846.ZM2790@candle.brasslantern.com> Date: Mon, 13 Mar 2000 17:08:46 +0000 In-Reply-To: <200003131649.RAA00105@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: PATCH: Re: The `zle' command and traps" (Mar 13, 5:49pm) References: <200003131649.RAA00105@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: Sven Wischnowsky , zsh-workers@sunsite.auc.dk Subject: Re: PATCH: Re: The `zle' command and traps MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 13, 5:49pm, Sven Wischnowsky wrote: } Subject: Re: PATCH: Re: The `zle' command and traps } } After a bit of checking... I think in many places where we call } zerrnam() we should really be calling zwarnnam() in functions } implementing builtins. Otherwise a error reported by the builtin will } exits loops and sublists and whatnot. I think this is done because it's so difficult (still) to stop/kill a loop that contains nothing but builtins. If you've got a builtin going wrong and that prevents the loop from ever reaching the end ... We really need to figure out how to handle interrupts during builtins before we start fooling with clearing errflag in additional cases. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com