Re: BUG REPORT: Custom Unwanted Face/Color interaction

Jan> I think I know how to solve this (and the MULE font problem) as Jan> follows Jan> 1. custom adds it stuff to the specifier with a 'custom tag. Jan> 2. reset-face is replaced by Jan> '(remove-all-face-specifier-entries-with-tag face '(custom)) Jan> This changes the way custom specs work. Custom will override only Jan> those settings it actually sets. Thus it Jan> 1. Will not mess with colors when setting the fonts. Jan> 2. Will leave defaults/resources alone by not deleting their Jan> specifier entries. Thus it the call to 'x-init-global-faces is no Jan> longer necessary, nor are the calls to init-face-from-resources Jan> 3. It no longer destroys the Mule info. Jan> 4. Will probably make it incompatible with FSF 20.3 Jan> However I think it is too late to do it for 21.0. This is what per Jan> meant with discussing this in Tsukuba. I'm a novice with custom, but your suggestion has the right `feel' for a good fix. Customize should try hard not to be `all or nothing'. Jan> P.S. Do you think the font-menu should not use custom? Currently Jan> custom is used for all things in the Options menu (and only those). Jan> Isn't that consistent? Hey, I'm just a dumb user who wants things to `just work'.