> 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((dx
> scrolling does not fix the problem. the framebuffer
> is wrong. forcing faces to redraw does fix the problem.
> i don't have enough screen real estate so faces is sometimes
> partially obscured by acme. the tear appears to be in line
> with the top of acme's window. in testing just now it
> h
> what changed recently?
> not drawterm.
no. not drawterm. not the video card.
i've recently "upgraded" x.
; ls -l `{which drawterm}
-rwxr-xr-x 1 quanstro users 1226424 Mar 12 2009
/home/quanstro/bin/amd64/drawterm
but that may be a red herring, see below
> can you tell us m
On Fri, Oct 16, 2009 at 1:02 PM, erik quanstrom wrote:
> i've recently been suffering from tearing in drawterm
> http://www.quanstro.net/9fans/tear.png
>
> ; xrdb -symbols | grep REL
> -DRELEASE=10503000
what changed recently?
not drawterm.
i'm not claiming drawterm is bug-free, but there must
