Re: emacs-unicode-2 fontset bug

[Kenichi Handa]

In article <address@hidden>, Leon <address@hidden> writes:

> After many trials, I think I found another bug of emacs-unicode-2
> branch. I have the following settings in ~/.Xresources:

> ,----[ ~/.Xresources ]
> | Emacs.Fontset-0: -*-*-medium-r-*-*-16-*-*-*-*-*-fontset-unicode,\
> | ascii:-*-terminus-medium-r-*-*-16-*-*-*-*-iso8859-1,\
> | mule-unicode-2500-33ff:-gnu-unifont-medium-r-*-*-16-*-*-*-*-*-iso10646-1,\
> | mule-unicode-e000-ffff:-gnu-unifont-medium-r-*-*-16-*-*-*-*-*-iso10646-1,\
> | mule-unicode-0100-24ff:-gnu-unifont-medium-r-*-*-16-*-*-*-*-*-iso10646-1
> | Emacs.Font: fontset-unicode
> `----

> In emacs-unicode-2, the font for ascii will be a font that matches 
> "-*-*-medium-r-*-*-16-*-*-*-*-*" instead of
> "-*-terminus-medium-r-*-*-16-*-*-*-*-iso8859-1".

> However, emacs 21.3 will correctly pick up the font matches
> "-*-terminus-medium-r-*-*-16-*-*-*-*-iso8859-1". 

I can't reproduce that bug here (Debian+XFree86) with the
latest emacs-unicode-2.  With the above setting, Emacs
starts up using a terminus font, and C-u C-x = on various
characters tells that terminus fonts are being used.

Have you tested it by starting Emacs with "-q"?

What is the output of M-x describe-face RET default RET?

---
Kenichi Handa
address@hidden