From: Tom Rauchenwald <sehnsucht.nach.unendlichkeit@quantentunnel.de>
To: Miles Bader <miles@gnu.org>
Cc: Herbert Euler <herberteuler@hotmail.com>, emacs-devel@gnu.org
Subject: Re: Font names in emacs-unicode-2 not recognized any more
Date: Wed, 30 Jan 2008 20:06:22 +0100 [thread overview]
Message-ID: <87tzkvnnf5.fsf@sec.modprobe.de> (raw)
In-Reply-To: <8763xb6vob.fsf@catnip.gol.com> (Miles Bader's message of "Thu, 31 Jan 2008 03:00:04 +0900")
Miles Bader <miles@gnu.org> writes:
> Miles Bader <miles@gnu.org> writes:
>>> After updating the source code of the emacs-unicode-2 branch, I get an
>>> error with my previously working configuration file. I have the
>>> following in my configuration file (~/.emacs):
>>
>> Some macros in configure.in were changed, so it seems that probably some
>> font-related configuration setting is not properly being done anymore.
>
> Looking at it, it seems that probably these lines (which I added, so I
> probably did wrong) in "configure.in":
>
> OPTION_DEFAULT_OFF([freetype],[use -lfreetype for local fonts support])
> OPTION_DEFAULT_OFF([xft],[use -lXft for anti aliased fonts])
>
> Should probably be "default on" instead, e.g.:
>
> OPTION_DEFAULT_ON([freetype],[don't use freetype for local font support])
> OPTION_DEFAULT_ON([xft],[don't use xft for anti aliased fonts])
>
> Can you try making that change, and see it works for you?
>
> [Remember to re-generate the configure script first using autoconf
> (i.e., just type "autoconf"); the Makefile should take care of
> re-running the configure script I think.]
That fixed it for me, thanks.
> Thanks,
>
> -Miles
Tom
next prev parent reply other threads:[~2008-01-30 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 15:00 Font names in emacs-unicode-2 not recognized any more Herbert Euler
2008-01-30 17:03 ` Miles Bader
2008-01-30 18:00 ` Miles Bader
2008-01-30 19:06 ` Tom Rauchenwald [this message]
2008-01-30 22:15 ` Miles Bader
2008-01-31 0:18 ` Herbert Euler
2008-01-31 1:22 ` Kenichi Handa
2008-01-31 1:40 ` Miles Bader
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=87tzkvnnf5.fsf@sec.modprobe.de \
--to=sehnsucht.nach.unendlichkeit@quantentunnel.de \
--cc=emacs-devel@gnu.org \
--cc=herberteuler@hotmail.com \
--cc=miles@gnu.org \
/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.