Eli-Zaretskii

The subtle bug in Emacs which caused this should be fixed now, thanks. I must note, though, that updating the mode line with such a high frequency is not a...

It will cause at least part of the problems, yes. What this dies is modify a non-current buffer at high frequency, so the main redisplay optimization of updating only the...

Sorry, I meant "does", not "dies".

> Seems this is unavoidable because the whole idea of this package is to show info in the echo area. Does the info change every 100 milliseconds? If not, how...

Thanks, but the backtrace alone is not enough: it doesn't convey enough information to understand how this happened. It appears that `display_count_lines` was called with the value of `start_byte` at...

Also, the value of `count` (681760) is greater than its value at function entry (681823), but the value of `start_byte` didn't change. How could that happen? Perhaps the values displayed...

I'm confused by this part of the recipe: Press i (Info-index) and select the first item. Pressing `i` doesn't display any items, it prompts for a subject, so how can...

Thanks. You are crazy^H^H^H^H^Hoverly optimistic calling `format-mode-line` (which exposes the display-engine code to Lisp) from an advice that wraps `message` (which is itself an entry point to redisplay). But the...

Thanks, should be fixed now.

I'm not familiar with the code enough to answer that. The issue is that `format-mode-line` is called as side effect of calling `message`, when the buffer's restriction was changed, but...