Re: wierd color problem with xemacs-21.0-b57

Kyle> Custom can't possibly customize faces under XEmacs Kyle> completely correctly until it [works through specifiers]. X Kyle> vs. TTY is one of the things that you can't get right unless Kyle> you deal with specifiers. Mule is another. It is currently [since the old Options code got disabled] simply not possible to change most non-ISO-8859-1 fonts (that means family, face, size, slant, weight, or any other tweaking you might have thought of doing, except color) without writing Lisp code in Mule XEmacs. (Hrvoje probably has no problems with ISO-8859-2 since he doesn't use Mule.) Kyle> So there isn't anything to debug, unless you're going to Kyle> convert Custom to use specifiers, which doesn't sound like Kyle> what you have in mind. Doing this conversion is on the Kyle> global TODO list... Well ... gold bars and slave girls aren't my problem, but I don't have much time right now. However it's pretty clear that every time somebody uses Custom functions to change faces Mule fonts are going to get hosed (potentially quite badly) and there is a risk every time Custom itself gets tweaked that the necessary incantations to save Mule from Custom may change. So I'm taking notes on Custom with that in mind. I won't get to it soon (maybe January?), so if anybody else wants to work on it in the meantime, I'll be happy to pass on my notes. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."