Clever. I've done that before, about a billion years ago. So what I get is that it runs: (font-menu-set-font nil nil 140) which by itself is not very useful if I plug it into the end of my init file. So I went digging through the source to see where font-menu-set-font is defined and what it's loaded from and what else is required, blah blah, having really no idea what I'm doing, but being willing to experiement a bit. I figure I need to load one of the font-menu.el modules in the source lisp directory. There are about four of them. Then I learn that the args in font-menu-set-font are family, weight, and size. In custom.el when I set a face, family becomes a quoted string, so I set that to "courier". I figure weight is irrelevant, so I put nil as a placeholder, and I'm trying to set it to 14 (whatever it is - pixels, points???), and in the example it says 140. I don't know why the multiple of 10, but I experimented with 120, and I eval'ed, and it sort of worked. I didn't put it in the init file yet, just came up the way I usually do, then eval'ed that form. Finally, I put a of each of the font-menu modules in turn in init.el, followed by (font-menu-set-font "courier nil 140). It almost works, except the alignment in shell buffers is not nice. This all seems like a harebrained way to do what I want to do, and probably fragile as well, but I'm almost there. And will not be deeply upset if I can't get the last piece. Thanks for that lead. It almost worked. -- Lynn David Newton Columbus, Ohio neologisticsediting.com lynndavidnewton.com _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Right, my description isn't real helpful, is it? All I mean by the end result is that it doesn't use the right font, and it looks like it's a proportional font, and when doing something like ls -AF in a large directory it doesn't line up in columns the right way. To be more specific I'd have to reproduce the problem again and probably put up a window dump image somewhere, which I could certainly do. But I've decided to live with it for a while in the current condition. It's not that bad, and in fact my 21.5 configuration is now nicer than my 21.4 ever was, so I'm pretty happy about that. Eventually, when I clear out some other problems (including stuff that has nothing to do with XEmacs) I'll probably revisit the problem and see if I can make it even better, working out some of the remaining nits. There's always something, isn't there? I'll also have to try digging into XResources again. Right, okay. All the more reason to leave well enough alone for the time being. Thanks to everyone. I'll be around. -- Lynn David Newton Columbus, Ohio neologisticsediting.com lynndavidnewton.com _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta