From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: `set-frame-font' doesn't support font aliases Date: Wed, 04 Jun 2008 20:49:43 +0900 Message-ID: References: <87fxrxpw0z.fsf@dekooning.omnisys.int.com.br> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1212580201 18890 80.91.229.12 (4 Jun 2008 11:50:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 4 Jun 2008 11:50:01 +0000 (UTC) Cc: eduardoochs@gmail.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 04 13:50:43 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K3rVq-00017z-C3 for ged-emacs-devel@m.gmane.org; Wed, 04 Jun 2008 13:50:42 +0200 Original-Received: from localhost ([127.0.0.1]:55197 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3rV3-00011Q-Um for ged-emacs-devel@m.gmane.org; Wed, 04 Jun 2008 07:49:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K3rUz-00011I-3X for emacs-devel@gnu.org; Wed, 04 Jun 2008 07:49:49 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K3rUy-000116-Iq for emacs-devel@gnu.org; Wed, 04 Jun 2008 07:49:48 -0400 Original-Received: from [199.232.76.173] (port=54146 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3rUy-000113-Dt for emacs-devel@gnu.org; Wed, 04 Jun 2008 07:49:48 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:43342) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K3rUx-000279-Uu for emacs-devel@gnu.org; Wed, 04 Jun 2008 07:49:48 -0400 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id m54Bo6An014335; Wed, 4 Jun 2008 20:50:06 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp1.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id m54BniHn026856; Wed, 4 Jun 2008 20:49:44 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id m54BnhgX025695; Wed, 4 Jun 2008 20:49:43 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1K3rUt-0001X3-P7; Wed, 04 Jun 2008 20:49:43 +0900 In-reply-to: (message from Stefan Monnier on Tue, 03 Jun 2008 04:22:36 -0400) 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) X-detected-kernel: by monty-python.gnu.org: Solaris 9 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:98381 Archived-At: In article , Stefan Monnier 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 instead: (set-frame-font ":alias=fixed") --- Kenichi Handa handa@ni.aist.go.jp