From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: font-related hanging / general brokenness Date: Thu, 19 Jun 2008 13:52:14 +0900 Message-ID: References: Reply-To: Miles Bader NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1213851164 22058 80.91.229.12 (19 Jun 2008 04:52:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Jun 2008 04:52:44 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 19 06:53:28 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 1K9C9A-0003DK-Q9 for ged-emacs-devel@m.gmane.org; Thu, 19 Jun 2008 06:53:21 +0200 Original-Received: from localhost ([127.0.0.1]:34340 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K9C8M-0004pj-7W for ged-emacs-devel@m.gmane.org; Thu, 19 Jun 2008 00:52:30 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K9C8F-0004pH-Om for emacs-devel@gnu.org; Thu, 19 Jun 2008 00:52:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K9C8F-0004p1-01 for emacs-devel@gnu.org; Thu, 19 Jun 2008 00:52:23 -0400 Original-Received: from [199.232.76.173] (port=42114 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K9C8E-0004ou-Qt for emacs-devel@gnu.org; Thu, 19 Jun 2008 00:52:22 -0400 Original-Received: from tyo202.gate.nec.co.jp ([202.32.8.206]:59818) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K9C8A-0004WC-Vj; Thu, 19 Jun 2008 00:52:19 -0400 Original-Received: from relay11.aps.necel.com ([10.29.19.46]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id m5J4qFuH010802; Thu, 19 Jun 2008 13:52:15 +0900 (JST) Original-Received: from relay11.aps.necel.com ([10.29.19.16] [10.29.19.16]) by relay11.aps.necel.com with ESMTP; Thu, 19 Jun 2008 13:52:15 +0900 Original-Received: from dhapc248.dev.necel.com ([10.114.112.215] [10.114.112.215]) by relay11.aps.necel.com with ESMTP; Thu, 19 Jun 2008 13:52:15 +0900 Original-Received: by dhapc248.dev.necel.com (Postfix, from userid 31295) id F39443AA; Thu, 19 Jun 2008 13:52:14 +0900 (JST) System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: (Miles Bader's message of "Thu, 19 Jun 2008 13:35:35 +0900") Original-Lines: 25 X-detected-kernel: by monty-python.gnu.org: Solaris 8 (1) 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:99432 Archived-At: I wrote: > Is having a :foundry as a face-attribute really the right thing? I > think users usually don't know or care about the foundry info, and its > presence as part of the face seems like it will cause the :family > attribute almost never work correctly (because a face which specifies > :family will almost always inherit an incorrect :foundry value from the > default face). BTW, one possible way to make :foundry work better might be to be _very_ relaxed about matching with it: First try matching including the face's :foundry, and if that returns "no match", then try matching agains with :foundy "*". That would allow the user to specify a foundry for special cases where it's desired -- probably almost always together with a family name -- but avoid the undesirable effects caused by inheriting a :foundry attribute. -Miles -- (\(\ (^.^) (")") *This is the cute bunny virus, please copy this into your sig so it can spread.