Re: What triggers a redisplay when no command or timer?

[Keith David Bershatsky <esq@lawlist.com>]

Thank you, Eli, for teaching me to make better use of the gdb breakpoint facilities and for letting me know that Emacs may not be responsible for triggering the redisplay at issue.  I look forward to examining this issue further as time permits.

Your help and insight is greatly appreciated.

Keith

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

DATE:  [09-07-2017 07:50:20] <07 Sep 2017 17:50:20 +0300>
FROM:  Eli Zaretskii <eliz@gnu.org>
> 
> * * *
> 
> I don't see here what you describe.  Emacs is sitting doing nothing
> and not entering redisplay, if I take care not to move the mouse
> and/or having the Emacs frame have focus.
> 
> But you don't need us to answer your question: just run Emacs under a
> debugger, put a breakpoint in redisplay_internal, and when it breaks,
> look at the backtrace.  If you cannot figure out what you see, post
> the backtrace here.
> 
> In general any event provided by any input source, including messages
> from the window-system, could potentially cause what you describe.
> 
> Note that the trace message you are citing means just that Emacs
> entered redisplay, but it doesn't mean something will actually be
> redisplayed, because redisplay_internal could return right away under
> some conditions.