Re: Customize bug?

Per> I'm not sure that is conceptually right. X resources gives Per> the ability to make "per display" customizations, while Per> customize only support customizations based on some broad Per> display categories. The most specific should win. E.g. you Per> may want to select different font sizes for different sized Per> monitors , something customize cannot know about. But specifiers could know this (not implemented in the current specifier code) if the server for the display gives the correct information (which it rarely does, except by accident), font.el does know this subject to the same caveat, and specifiers definitely can handle this on a user-controlled basis by defining specifier tags to correspond to the known displays. -BP> But with a decent font model, you could say 'I want a 1inch -BP> high font' and it would work everywhere, no matter your -BP> monitor size or pixel resolution. :) Um, no, I don't want a one inch high font; I want a 3-inch high font on my projection monitor's 3-meter screen, giving 30 lines, a 20-point font on my 21" monitor, and 16-point font on my 14" normally-only-the- server-console display. All making somewhat different tradeoffs of line count for readability. This is beyond current font model technology, I believe.... -- 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."