Re: Customize bug?

Hrvoje Niksic <hniksic(a)srce.hr&gt; writes: > The unbundled code had, however, other problems; for instance, I > recall that you couldn't dump XEmacs with code that used `defface'. Yep. I suspect it is still the case for Emacs. It is probably less of a problem in the Emacs cathedral than in the XEmacs bazaar. > True. font.el provides some of the needed functionality, but it's way > too naive to be taken seriously (no offense Bill!) Not to mention > that the redisplay doesn't support merging of font properties. Right, but font.el gives you the ability to write code that works as well as the current display code will allow, and that will work better (with no changes to the code) as the display model grows more powerful. > It depends. I think the *default* customize settings (such as in > `defface' forms) should be overridden with X resources. On the other > hand, hand-changed customize settings (such as with `M-x customize-face') > should override X resources. I'm not sure that is conceptually right. X resources gives the ability to make "per display" customizations, while customize only support customizations based on some broad display categories. The most specific should win. E.g. you may want to select different font sizes for different sized monitors , something customize cannot know about.