Re: Customize bug?

Hrvoje Niksic writes: Hrvoje> It depends. I think the *default* customize settings (such as in Hrvoje> `defface' forms) should be overridden with X resources. On the other Hrvoje> hand, hand-changed customize settings (such as with `M-x Hrvoje> customize-face') should override X resources. The last bits of this thread also has the virtue of showing that there's currently not even a consensus on the priority of assignments, and not only because Custom or X resources can't really handle specifiers. While I agree with what Hrovje says here, I have the feeling that the face resources should go away in a medium-term. It's no good to have multiple interfaces to the same functionality, especially when those interfaces are either partially efficient, or doesn't interact very well with each other. My experience with X has always shown me that using the X resources mechanism for just about everything is a /bad thing/. X resources should be used _only_ for stuff that we _know_ only happen under X. Widgets backgrounds, size of frames etc. For instance, it's a nonsense to have an attributeBackground[Pixmap] resource for the default face which actually behaves almost like a background [pixmap] setting for the frame. The only thing that faces should inherit from X resources should be a general *foreground setting. Using X resources everywhere only confuse novice users, make the work harder for us, and we need another specification interface anyway. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19