Re: Who's maintaining the Win32 display code?

[David Abrahams]

David Abrahams <address@hidden> writes:

> Jason Rumney <address@hidden> writes:
>
>> David Abrahams <address@hidden> 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