On 11/01/2010 03:32 AM, John McCabe-Dansted wrote:
On Mon, Nov 1, 2010 at 1:09 PM, Vincent van Ravesteijn<v...@lyx.org> wrote:
On Wed, Oct 27, 2010 at 4:37 PM, John McCabe-Dansted<gma...@gmail.com> wrote:
Hi Vincent, this appears to be another recent regression, this time
from r35832 on Monday.
Sorry John, your system is a bit off. I can reproduce with r35831 too ;)
Incidentally, I think the regression in r35832 has to do with being
able to reproduce the bug when LFUNs.lyx is marked readonly, which in
turn is because r35832 does not set the readonly flag when opening
readonly files.
I then get the Assert:
This is a serious bug and needs to fixed quickly. It would be very
helpful if you could bisect further.
The actual bug itself appears to have been introduced in r34826 by "rgheck".
Yes, we expected there would be some such things: This was the big
change to how updateBuffer() is called. So there is probably a missing
call to updateBuffer() somewhere, that leads to the TOC being empty.
I don't understand the split screen stuff, so I'm not sure why this
would only happen then. But here's a simple recipe to reproduce.
1. Open LyX. Create a section heading (alt-P, 2) with an x in it.
2. Split the screen.
3. File>New
4. Go back to the top, where the 'x' is, and type something.
Note that this only happens if the new, empty file is displayed in the
lower region. If the "x" file is displayed both times, you do not get
the crash.
Richard
