Re: Issues with partial repainting when enabling cairo

[Eli Zaretskii <eliz@gnu.org>]

> From: Yuri D'Elia <wavexx@thregr.org>
> Date: Fri, 27 Jan 2017 17:39:17 +0100
> 
> On Fri, Jan 27 2017, Eli Zaretskii wrote:
> >> There are some bug reports about cairo on the bts, but nothing so
> >> glaring.
> >
> > Glaring display bugs are the main problem with Cairo, AFAIK.  We need
> > motivated individuals who'd work on debugging and fixing those
> > problems.
> 
> Apart from being newer, is there any advantage that cairo should bring
> to the display engine?

It's supposed to be the future of GUI desktop on Unix, beyond Xlib
interface and the traditional X server-client setup, so I think it's
important for us to move in that direction.

> When I was reading the display code (for debugging the line truncation
> hang some months ago) it didn't seem quickly approachable to the
> uninitiated. In addition, there's quite some historical baggage one
> needs to consider.

You are talking about xdisp.c, which is entirely irrelevant to Cairo.
The Cairo-related code is in xterm.c and xfns.c (and also in
ftcrfont.c (the "font driver") and in image.c, but those are most
probably unrelated to what you see).

> Each time I read the internals I can get further, but I've been using
> emacs for 10+ years, and I wonder what kind of guru one needs to be to
> have the balls^H^H^H^Hbeard to fix cairo ;)

The trick is to investigate specific problems without trying to
understand the entire big picture.  I'm quite sure the basic design of
the Cairo support is sound, the bugs are in minor details.

Let me know if you need some guidance in finding the places where the
scroll-related problems you saw could hide.

TIA