From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon, 19 Oct 2009 12:46:49 -0400
To: 9fans@9fans.net
Message-ID: <09c8bc76b8477e66837154fe234855de@ladd.quanstro.net>
In-Reply-To: <<dd6fe68a0910190937p13b0ba0fk77f51ef5541d19f8@mail.gmail.com>>
References: <<dd6fe68a0910190937p13b0ba0fk77f51ef5541d19f8@mail.gmail.com>>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] drawterm tearing
Topicbox-Message-UUID: 8b9b1860-ead5-11e9-9d60-3106f5b1d025

> 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 = dst->X) == 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.

does fix!

curiosity: is this a locking problem or an arithmetic
problem?

- erik