From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <d87186e8931abd4f69813248a8bd35db@ladd.quanstro.net>
References: <d87186e8931abd4f69813248a8bd35db@ladd.quanstro.net>
Date: Mon, 19 Oct 2009 09:37:13 -0700
Message-ID: <dd6fe68a0910190937p13b0ba0fk77f51ef5541d19f8@mail.gmail.com>
Subject: Re: [9fans] drawterm tearing
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 8b7ac7ae-ead5-11e9-9d60-3106f5b1d025

> scrolling does not fix the problem. =C2=A0the framebuffer
> is wrong. =C2=A0forcing faces to redraw does fix the problem.
> i don't have enough screen real estate so faces is sometimes
> partially obscured by acme. =C2=A0the tear appears to be in line
> with the top of acme's window. =C2=A0in testing just now it
> happened 4/4 times with faces partially obscured and 0/3
> times with faces not obscured.

great. now that you have a reproducible test case, try this:

in drawterm/gui-x11/x11.c:/^xdraw it says

        /*
         * drawterm was distributed for years with
         * "return 0;" right here.
         * maybe we should give up on all this?
         */

        if((dxm =3D dst->X) =3D=3D nil)
                return 0;

try adding an unconditional "return 0;"
right there and see if the problem goes away.
if so, problem solved, or at least pinned on
some combination of the drawterm x11 code
and the new x11 server you have.
that code is trying to do a good job when
x11 is on the other end of a network connection,
but that case is getting less and less important.

russ