From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Abrahams Newsgroups: gmane.emacs.devel Subject: Re: Who's maintaining the Win32 display code? Date: Tue, 23 Sep 2003 19:50:28 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20030916.182537.01367130.Takaaki.Ota@am.sony.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1064361388 16125 80.91.224.253 (23 Sep 2003 23:56:28 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 23 Sep 2003 23:56:28 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Sep 24 01:56:26 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1A1x18-00065v-00 for ; Wed, 24 Sep 2003 01:56:26 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1A1x7c-0002Rr-00 for ; Wed, 24 Sep 2003 02:03:08 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.22) id 1A1x0U-00011i-Fn for emacs-devel@quimby.gnus.org; Tue, 23 Sep 2003 19:55:46 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.22) id 1A1wvk-0008Cw-N2 for emacs-devel@gnu.org; Tue, 23 Sep 2003 19:50:52 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.22) id 1A1wvX-0007nP-Sl for emacs-devel@gnu.org; Tue, 23 Sep 2003 19:50:40 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.22) id 1A1wvQ-0007dT-W2 for emacs-devel@gnu.org; Tue, 23 Sep 2003 19:50:33 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1A1wuv-0007zY-00 for ; Wed, 24 Sep 2003 01:50:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1A1wuu-0007zQ-00 for ; Wed, 24 Sep 2003 01:50:00 +0200 Original-Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 1A1wvN-00045U-00 for ; Wed, 24 Sep 2003 01:50:29 +0200 Original-Lines: 48 Original-X-Complaints-To: usenet@sea.gmane.org User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (windows-nt) Cancel-Lock: sha1:DGTlU046r2mrw5uvw0ShphDAkEo= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:16583 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:16583 David Abrahams writes: > Jason Rumney writes: > >> David Abrahams writes: >> >>> FWIW, I don't even know what "BDF font" is. >> >> Strange, since the stack trace shows clearly that you are using one, >> and it is not possible to use BDF fonts on Windows accidently. > > Maybe that's a symptom of the bug here. The only fonts I'm using are > AFAICT standard Windows TrueType fonts that come with the system. > The relevant section of my .emacs is: > > ; is it gnu emacs or xemacs > (setq my-gnup (not (string-match "^\\(XEmacs\\).*" (emacs-version)))) > > (setq my-windows > (or (eq system-type 'windows-nt) > (eq system-type 'cygwin32) > (eq system-type 'cygwin))) > > > (if my-gnup > (condition-case nil > (progn > (set-default-font "-*-Lucida Console-normal-r-*-*-12-96-96-96-c-*-iso8859-1") > (set-face-font 'italic "-*-Lucida Console-normal-i-*-*-12-96-96-96-c-*-*-1") > (set-face-font 'bold-italic "-*-Lucida Console-bold-i-*-*-12-96-96-96-c-*-*-1") > ) > (error nil))) > > There is no other font selection going on anywhere, at least not > AFAICT. And furthermore, having set a breakpoint in w32_BDF_TextOut I can confirm that emacs doesn't try to draw any BDF fonts for me when operating normally. I think the fact that it arrives there in the first place is a symptom of whatever's gone wrong before. That's a pretty strong clue. Does anyone know this code well enough to use that to make progress on this bug? -- Dave Abrahams Boost Consulting www.boost-consulting.com