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: fail on osx between 2/4/2009 and 2/5/2009 Date: Tue, 17 Feb 2009 20:15:14 +0900 Message-ID: References: <861vubqc79.fsf@blue.stonehenge.com> <10DD5733-4089-4A60-B090-4CB5E32A0E19@42tools.com> <49917BE9.6020903@gnu.org> <15A24001-137F-469F-8B05-DB31D4E8995D@gmail.com> <86BB7F5A-18D1-4D15-A141-FC721BCC7CB4@gmail.com> NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1234869323 14916 80.91.229.12 (17 Feb 2009 11:15:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 17 Feb 2009 11:15:23 +0000 (UTC) Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org To: Adrian Robert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 17 12:16:38 2009 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 1LZNwK-0005oq-P5 for ged-emacs-devel@m.gmane.org; Tue, 17 Feb 2009 12:16:37 +0100 Original-Received: from localhost ([127.0.0.1]:54139 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZNv0-0006Q6-Bw for ged-emacs-devel@m.gmane.org; Tue, 17 Feb 2009 06:15:14 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LZNuv-0006Pg-Hc for emacs-devel@gnu.org; Tue, 17 Feb 2009 06:15:09 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LZNut-0006PN-Ri for emacs-devel@gnu.org; Tue, 17 Feb 2009 06:15:09 -0500 Original-Received: from [199.232.76.173] (port=33701 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZNut-0006PK-Pf for emacs-devel@gnu.org; Tue, 17 Feb 2009 06:15:07 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:61672) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LZNus-0002rp-EG for emacs-devel@gnu.org; Tue, 17 Feb 2009 06:15:07 -0500 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id n1HBF0XY017988; Tue, 17 Feb 2009 20:15:00 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp1.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id n1HBF0xB002998; Tue, 17 Feb 2009 20:15:00 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id n1HBEx1F001345; Tue, 17 Feb 2009 20:14:59 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 4.69) (envelope-from ) id 1LZNv0-0003sq-L9; Tue, 17 Feb 2009 20:15:14 +0900 In-reply-to: (message from Adrian Robert on Tue, 17 Feb 2009 12:15:42 +0200) X-detected-operating-system: 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:109125 Archived-At: In article , Adrian Robert writes: > I meant my question more from a user perspective. If they call 'set- > frame-font or similar, do ALL of the fonts, on, e.g., the HELLO > screen, get switched to be the most similar to the user's selection > with the appropriate charset, or does it just change the ASCII font? Yes, at least that is the intention. > Experimenting with the non-freetype X build here, just set-frame-font > doesn't seem to do it, but selecting something from the shift-left- > mouse menu does (but I can't fully trace out what is getting called > in this case). Then, it seems that there's a bug somewhere. I'll work on it. >>> Also, is there a plan to update the documentation for match() and >>> list >>> () in font.h? I'm willing to do this (after I've finished and tested >>> my new implementation) if no one else has time. > > > > I don't know what else should be added to the > > documentations, but if you think the current ones must be > > improved, please go ahead. > The full list of properties that can appear bundled under the > FONT_EXTRA property that are important for drivers to take into > account in match() and list() should be specified somewhere in font.h. Ah, I see what you mean. > In font.c there is font_property_table, which lists everything that > is a "first class" property in font.h (explicitly listed in > font_property_index), plus the following: 'lang', 'script', and > 'otf'. While the font-spec function mentions 'script' and 'name', > but not 'lang' or 'otf'. I'm not sure about the criterion for > putting something under "EXTRA" or listing it in one place or another > in font.c, but if the font driver should respond to it, especially > for something as important as core emacs font selection, it should be > mentioned in font.h. Ok, I'll document them. --- Kenichi Handa handa@m17n.org