Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Infinite loop (bug in wordcode evaluation?)
- X-seq: zsh-workers 9573
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: Infinite loop (bug in wordcode evaluation?)
- Date: Fri, 4 Feb 2000 16:31:39 +0000
- In-reply-to: <200002040908.KAA21594@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <200002040908.KAA21594@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author