Martin Buchholz <martin(a)xemacs.org&gt; writes: So it does work according to plan (not sure why it is flashing, there really shouldn't be any redisplay in between those settings). It is just that in your case the plan is not working :-). Please cut custom some slack. It has already improved a lot. It used to be that you got white on black after using the font menu. Then you got black on gray always. Now you get your original colors black. The only thing custom cannot restore currently is settings that are dynamically changed using lisp. I am afraid it is 'no can do' for the moment. Except to give font-menu a variable to not use custom. I think I know how to solve this (and the MULE font problem) as follows 1. custom adds it stuff to the specifier with a 'custom tag. 2. reset-face is replaced by '(remove-all-face-specifier-entries-with-tag face '(custom)) This changes the way custom specs work. Custom will override only those settings it actually sets. Thus it 1. Will not mess with colors when setting the fonts. 2. Will leave defaults/resources alone by not deleting their specifier entries. Thus it the call to 'x-init-global-faces is no longer necessary, nor are the calls to init-face-from-resources 3. It no longer destroys the Mule info. 4. Will probably make it incompatible with FSF 20.3 However I think it is too late to do it for 21.0. This is what per meant with discussing this in Tsukuba. Jan P.S. Do you think the font-menu should not use custom? Currently custom is used for all things in the Options menu (and only those). Isn't that consistent?