all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Cc: "Jan D." <jan.h.d@swipnet.se>
Subject: Re: /srv/bzr/emacs/trunk r99850: Lucid menus can now use Xft for fonts.
Date: Thu, 08 Apr 2010 20:08:41 +0200	[thread overview]
Message-ID: <87iq81izpy.fsf@telefonica.net> (raw)
In-Reply-To: 87tyrlj0zo.fsf@telefonica.net

Óscar Fuentes <ofv@wanadoo.es> writes:

> "Jan D." <jan.h.d@swipnet.se> writes:
>
>> ------------------------------------------------------------
>> revno: 99850 [merge]
>> committer: Jan D. <jan.h.d@swipnet.se>
>> branch nick: trunk
>> timestamp: Thu 2010-04-08 18:21:25 +0200
>> message:
>>   Lucid menus can now use Xft for fonts.
>>   
>>   * xsettings.c (current_font, SYSTEM_FONT, XSETTINGS_FONT_NAME): New.
>>   (parse_xft_settings): Also check for XSETTINGS_FONT_NAME and save that
>>   in current_font.
>>   (init_gconf): Read value of SYSTEM_FONT and save it in current_font.
>
> [snip]
>
> This change breaks the build for me.
>
> #define XSETTINGS_FONT_NAME is within a #ifdef HAVE_GCONF ... #endif but
> it is used without that condition. This is a KDE machine, so HAVE_GCONF
> is undefined here. (I'll love to see nice fonts on menus, though ;-)

BTW, moving the

#define XSETTINGS_FONT_NAME  "Gtk/FontName"

outside the #ifdef HAVE_GCONF ... #endif fixes the build. The menus now
look great. Thanks!





  reply	other threads:[~2010-04-08 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NzvM8-00057k-3x@internal.in.savannah.gnu.org>
2010-04-08 17:41 ` /srv/bzr/emacs/trunk r99850: Lucid menus can now use Xft for fonts Óscar Fuentes
2010-04-08 18:08   ` Óscar Fuentes [this message]
2010-04-08 18:24   ` Jan Djärv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iq81izpy.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.