Mats> I have failed for the buffer tabs and the menus. Is there Mats> some way to control the fonts there? At startup using X resources I have XEmacs*Tabs.xftFont: Bitstream Vera Sans-12:dpi=100 XEmacs*menubar*xftFont: Bitstream Vera Sans-12:Bold:dpi=100 XEmacs.modeline.attributeFont: Bitstream Charter-12:dpi=100 XEmacs.default.attributeFont: Bitstream Vera Sans Mono-12:dpi=100 There doesn't seem to be a way to get at them via faces, so there's probably not much you can do from Lisp. YMMV, but I'd like to point out the modeline font. It's proportional, so I get a *lot* more information in the modelines. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

Mats> Aha. Much better now. I had missed the xftFont-thing Mats> completely. RTFM? It may only be in the Internals manual. Remind me to check :-) Mats> But I still can't get the tabs font to change. It seems like Mats> the hight of the tab changes but not the font. Ideas? Post the resources you're using, and also the chatter from the Xft debug messages. (Set xft-debug-level > 0, 1 should be enough.) -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

sjt> Post the resources you're using, and also the chatter from sjt> the Xft debug messages. (Set xft-debug-level > 0, 1 should sjt> be enough.) Mats> * Resources Mats> * Chatter It all looks normal to me. Check your Installation and make sure that you explicitly specified --with-xft=tabs,... (there were bugs in configure; --with-xft=all and bare --with-xft didn't work for many people). Also, if you can, try running xemacs under a debugger and use the debugger's set command to set debug_tabs=3 before starting XEmacs. This will produce a huge amount of chatter, so you don't want to run that way for very long. But I think the information we need is printed out during initialization, so probably you can just shut it down after that. I think you can just grep stderr for "^font: name=", which should give the information we need. BTW, I just committed a new node "Xft Font Configuration" (a subnode of "Faces") to CVS. Next time you update and rebuild, take a look and let me know what you think. Don't hesitate to mention things that I obviously would have seen for myself, it will help to establish priorities. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

sjt> This is going to take a while; the lwlib/Xft/font-menu code sjt> is just altogether too messed up, so I'm going to have to do sjt> some general cleanup and refactoring in preparation. OK, this is still basically true. I have fixed one simple bug, there's a patch on XEmacs Patches, and it's been committed to CVS. XEmacs will now properly parse your resources and use them. *For technical reasons, I had to change the name of the resource.* It is now fcFontName, class FcFontname for both tabs and menubar. Leaving the xftFont resources in your ~/.Xresources is probably a good idea; it should be a no-op, and eventually there will be an Xt converter to use xftFont resources directly. Getting rid of xftFont resources in favor of unifying all font resources is a longer-term project. However, there's a second, deeper problem, which is that there's code in glyphs-x.c to make the tab controls sortakinda rather unreliably pay attention to the 'buffers-tab face. That face is not updated from the tab control resources, but does inherit from other faces (I believe modeline is one). The upshot is that with debug_tabs > 0 you can observe situations where XEmacs uses the resource, but before you actually see it on the display, the face code changes it, and what you see on the display is a different font. Unfortunately, this doesn't always take, although I haven't been able to find a recipe to reproduce the case where the buffers-tab font is overridden by the Tabs.fcFontName resource font. For now, you can either set *both* the Tabs.fcFontName resource and the font in the buffers-tab face to your preferred font, or you can set the resource and use the following kludge patch (which will not be committed to CVS) to disable the buffers-tab face's font: diff --git a/src/glyphs-x.c b/src/glyphs-x.c index 5f48dc6..175e064 100644 --- a/src/glyphs-x.c +++ b/src/glyphs-x.c ＠＠ -2374,7 +2374,8 ＠＠ update_widget_face (widget_value* wv, Li #ifdef USE_XFT XftFont *rf = FONT_INSTANCE_X_XFTFONT (fi); - if (rf) + /* #### JUST FOR TESTIONG! */ + if (rf && !EQ (IMAGE_INSTANCE_WIDGET_TYPE (ii), Qtab_control)) { /* #### What to do about Motif? IIRC, Motif is shut out if we're using Xft, so it may be OK. I can't really promise either will work, but at least now you've got a fighting chance. :-) I also don't know how this affects the menubar, but since no problems have been reported with the menubar font and I haven't observed any in my testing, I have hope that this doesn't introduce a bug there. -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.