Kenichi Handa | 29 Sep 14:27 2006

Re: Xresource of enable-font-backend?

In article <m2k63owdan.fsf <at> sl392.st-edmunds.cam.ac.uk>, Leo <sdl.web <at> gmail.com> writes:

> There are some interesting discussions in XftGnuEmacs in
> emacswiki.org. Hope the developers can consider this.

> ----
>  Sept. 23, 2006: Is there an Xresource that is equivalent to the
>  command-line option ‘--enable-font-backend’ so that I don’t have to
>  type this every time I start Emacs?

> - Doesn’t seem to be. But it’s a trivial patch to src/emacs.c to flip
>   the command line arg to on-by-default, just reverse the sense of the
>   variable. I’m not entirely clear why one would compile in Xft
>   support and not use it at this stage (and on my system at least, the
>   unicode-2 branch doesn’t even display particularly sensibly unless
>   you turn it on…), so IMHO it would be nice (tm) if it was on by
>   default upstream.

I didn't know about that wiki site.  If you find a question
that can't be answered easily, could you please forward it
to here?  I think I don't have a time to check that wiki
site that frequently.

Anyway, the `--enable-font-backend' option will disappear as
soon as we can get rid of legacy font-handling codes.
Unfortunately, for Windows and Mac port, we still need them.

By the way, I've just added this note in README.Unicode.

----------------------------------------------------------------------
Which font backends to use can be specified by X resource
"FontBackend".  For instance, if you want to use Xft fonts only,

Emacs.FontBackend: xft

will work.  If this resource is not set, Emacs tries to use all font
backends available on your graphic device.
----------------------------------------------------------------------

Even if you set it, --enable-font-backend is still necessary
because Emacs calls font-related functions before it checks
above resource.

---
Kenichi Handa
handa <at> m17n.org

Gmane