Re: Redisplay problems?

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden, address@hidden, address@hidden, address@hidden,
>         address@hidden
> Date: Tue, 25 Mar 2014 09:10:44 -0400
> 
> Hmm... I guess it depends on what kind of drawing operations we use.
> E.g. if the redisplay optimizations include usage of "block move"
> operations, then indeed, if the redisplay happens before the expose, we
> may end up moving not-yet-drawn (i.e. incorrect/garbage) pixels.
> 
> Do we use things like "block move"?

Not sure what you mean by "block move".  From the name and the
context, it sounds like you are talking about actual drawing, i.e. on
a level that underlies the display back-ends in xterm.c, w32term.c
etc.  If so, that's way below the level of redisplay optimizations
that are in xdisp.c and even in dispnew.c, which are both
device-independent.

But maybe I misunderstand what you mean.