Re: No XFT in CVS from this morning

[Taylor Venable <taylor@metasyntax.net>]

On Tue, 17 Jun 2008 14:44:01 -0400
Taylor Venable <taylor@metasyntax.net> wrote:

> On Tue, 17 Jun 2008 13:08:12 -0400
> Chong Yidong <cyd@stupidchicken.com> wrote:
> 
> > Taylor Venable <taylor@metasyntax.net> writes:
> > 
> > >> > I built Emacs from CVS this morning, and there's no font
> > >> > anti-aliasing being done.
> > >> 
> > >> I can't reproduce this using latest CVS.  What font are you
> > >> using?
> > >
> > > From my .emacs file:
> > >
> > > (set-face-attribute 'default nil
> > >   :font "DejaVu Sans Mono-13" :slant 'normal :weight 'normal)
> > 
> > Working fine for me on i686-pc-linux-gnu, GTK+ Version 2.12.9,
> > latest CVS.
> 
> It takes a little while to compile on this system, so I've confirmed
> that it worked correctly on versions checked out for 2008-06-01 and
> 2008-06-08 but not when checked out with "cvs ... co -D yesterday"
> which leads me to think that something probably changed sometime
> within the last week.  Since it seems that nobody else is having
> problems, I'll give my library versions too:
> 
> 	gtk2+-2.12.9
> 	libXft-2.1.12
> 
> I've attached the output of the configure script, and the config.log
> (gzipped) -- if desired, I can attach the ones from the version as of
> 2008-06-08 as well, so they can be diff'd.

Based on repeated compilation, I've found that the change in behaviour
from properly anti-aliasing fonts to rendering them without anti-
aliasing comes from a change made on or after 2008-06-13; checkouts
made from versions before this date work fine, and checkouts made from
versions on or after this date produce the erroneous behaviour.  I see
from the ChangeLog that a lot of work was done then; perhaps one of
these changes is the one that causes the effects in my installation?

-- 
Taylor Venable            http://real.metasyntax.net:2357/

foldr = lambda f, i, l: (len(l) == 1 and [f(l[0], i)] or
                         [f(l[0], foldr(f, i, l[1:]))])[0]