Do not try to track_change an auto-deleted bibitem

We are not capable of handling two bibitems within one biblio paragraph.
That's why we have functions like Paragraph::brokenBiblio() and
Paragraph::fixBiblio(). So, if we fix the biblio by deleting the second
bibitem, we should not keep it as deleted.

This code caused a crash because the inset was released, but still kept as
deleted.

Fixes-bug: #8646.
This commit is contained in:
Vincent van Ravesteijn 2014-02-07 15:53:57 +01:00
parent a6fce04f39
commit e8242cbee6

View File

@ -3216,8 +3216,7 @@ int Paragraph::fixBiblio(Buffer const & buffer)
// these, which there should be.
// FIXME: why does it make sense to do that rather
// than keep the first? (JMarc)
Inset * inset = d->insetlist_.release(bibitem_pos);
eraseChar(bibitem_pos, track_changes);
Inset * inset = releaseInset(bibitem_pos);
d->insetlist_.begin()->inset = inset;
return -bibitem_pos;
}