From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4775 invoked from network); 4 Feb 2000 16:32:01 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 4 Feb 2000 16:32:01 -0000 Received: (qmail 83 invoked by alias); 4 Feb 2000 16:31:55 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9573 Received: (qmail 73 invoked from network); 4 Feb 2000 16:31:54 -0000 From: "Bart Schaefer" Message-Id: <1000204163139.ZM8570@candle.brasslantern.com> Date: Fri, 4 Feb 2000 16:31:39 +0000 In-Reply-To: <200002040908.KAA21594@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: Infinite loop (bug in wordcode evaluation?)" (Feb 4, 10:08am) References: <200002040908.KAA21594@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: Sven Wischnowsky , zsh-workers@sunsite.auc.dk Subject: Re: Infinite loop (bug in wordcode evaluation?) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Feb 4, 10:08am, Sven Wischnowsky wrote: } Subject: Re: Infinite loop (bug in wordcode evaluation?) } } Bart Schaefer wrote: } } > } The problem is that none of the functions in loop.c check if retflag } > } is set and hence don't return. } > } > I can't find any loop construct in 3.0.7 that produces this behavior, } > yet 3.0.7 does not have any of those extra retflag tests in loop.c. } > } > Does anyone know what else might have changed to cause this problem? } } Found it. getkey() in zle_main.c now resets `breaks' to the value it had } before, so that the new value stored in bin_break() set by the signal } handler doesn't make it through to the execution code. } } Dunno where this comes from, though. It came from zsh-workers/7038, something to do with making _read_comp work correctly. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com