GNU bug report logs - #19511
25.0.50; Failed assertions in redisplay() code. (dispnew.c:1405; xdisp.c:17524)

Previous Next

Full log

View this message in rfc822 format

From: Vitalie Spinu <spinuvit <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Andreas Matthias <andreas.matthias <at> gmail.com>, 19511-done <at> debbugs.gnu.org
Subject: bug#19511: 25.0.50; Failed assertions in redisplay() code. (dispnew.c:1405; xdisp.c:17524)
Date: Mon, 05 Jan 2015 08:59:02 -0800

 >>> Eli Zaretskii on Mon, 05 Jan 2015 17:58:05 +0200 wrote:

[...]

> I hope Polymode will be changed to not call bury-buffer in that
> situation (I always thought bury-buffer is strictly for interactive
> use, FWIW).

Bury-buffer is used to "hide" from the indirect buffer from the
user. That was the easiest way to implement that and should have been
rewritten anyways.

Removing it doesn't change the fact that buffers are switched
(with-current-buffer ...) inside font-lock-fontify-region-function. But
I guess that's not an issue (right?).

Would it be enough to remove `bury-buffer` call to get back the
optimization? What are other elisp functions that can potentially
invalidate window_end?

Thanks,

  Vitalie

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.