On Sat, Oct 21, 2006 at 12:22:51AM +0200, Enrico Forestieri wrote: > On Fri, Oct 20, 2006 at 09:36:29PM +0300, Martin Vermeer wrote: > > > On Fri, Oct 20, 2006 at 07:19:05PM +0200, Enrico Forestieri wrote: > > > On Fri, Oct 20, 2006 at 06:43:01PM +0200, Enrico Forestieri wrote: > > > > > > > I also managed to hang LyX with change tracking activated. To reproduce: > > > > - new document > > > > - create an ERT inset and write abc in it, followed by <return> > > > > - activate change tracking and press backspace (to delete the empty > > > > line) > > > > - select Document->Change Tracking->Accept All Changes > > > > Now the cpu goes to 100% and LyX doesn't respond anymore. > > > > > > This also happens without the patch. So, it seems to work, AFAICT. > > > > Cannot reproduce the bug you describe here -- 1.5 head on FC4. > > Sorry Martin, I should have specified that I was talking about 1.4.4cvs, > but I thought that it was clear given that the patch was for this version. > I didn't even try 1.5 as Michael is working on CT and warned about using it.
OK Enrico, I can confirm the bug. What's more, not only for ERT but for any collapsable inset. What's even more, it happens _outside_ any inset, in the main document. Even if there is text below the testing area. This is weird. What does 1.5 have that 1.4 doesn't? ...and the endless loop calls int LyXText::leftMargin(pit_type const pit, pos_type const pos) const in text.C (just happened to notice as I have an old lyxerr there) - Martin
pgp30B3G7enii.pgp
Description: PGP signature
