[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: `set-frame-font' doesn't support font aliases

From: Kenichi Handa
Subject: Re: `set-frame-font' doesn't support font aliases
Date: Wed, 04 Jun 2008 20:49:43 +0900
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

In article <address@hidden>, Stefan Monnier <address@hidden> writes:

>>> Can you recover the Emacs-22 behavior by restricting the backends to
>>> just `x'?

> > No, because the font-name parser is independent of font
> > backends; i.e. even if you use only x font-backend, you can
> > specify a font name as, for instance,
> > "fixed-12:foundry=misc".

> Then we need to detect the ambiguity, and provide a way for the user to
> resolve the ambiguity.

> > Another idea is to do:
> >   (set-frame-font (font-spec :alias "fixed)).
> > or
> >   (set-frame-font ":alias=fixed")

> That seems clean from the user's POV.  Tho maybe aliases should take
> precedence, rather than the reverse.

Something like this for "Bitstream Vera Sans"?
  ":family=Bitstream Vera Sans"

I don't like it because the new format is incompatible with
fontconfig's way.  So, the original question arises:

> Is keeping backward compatibility of (set-frame-font
> "fixed") important enough to drop the support of
> fontconfig-style name?

Or, isn't it good enough to ask users to use this form

(set-frame-font ":alias=fixed")

Kenichi Handa

reply via email to

[Prev in Thread] Current Thread [Next in Thread]