Re: [21.0b63] make-face-bold is broken under CYGWIN+X...

Jan> The upshot is that custom will probably still hose your Mule Jan> faces. :-( Jan> Maybe what it should do in addition to that is use not Jan> 'reset-face' but something similar that leaves all the fonts Jan> with the 'mule-font' tag alone. I don't think this works right. It postpones the day when Custom learns to handle mule fonts, too. :-/ Jan> What I really don't understand is how the FSF Emacs manages Jan> to use custom without destroying all of the Mule stuff. FSF uses explicit fontSets (instead of specifier magic which allows multiple fonts to coexist if they have different registries). I bet that this is implemented in such a way as to be equivalent to not using `reset-face'. Jan> Huh? Current ALL tag-sets are device tags. Some of them may Jan> be user defined but they are related to the device. In fact 'mule-font and 'default are not really "user-defined" even if they are created with `define-specifier-tag'. They aren't device tags. What's 'win? Jan> if it were possible to have efficient tags that worked at Jan> every locale it would be a lot easier to implement Custom Jan> atop of specifiers. (What do you mean by "efficient" and "work at every locale"?) Suppose I wanted to use a tag set? Paul's code doesn't allow for that; his code passes and expects to receive a symbol. It's probably simple enough to change that. My point is that it is not true that the tags are mutually exclusive, tag sets are necessary in general, and I don't know---and neither does anyone else, right?---about this particular code. If this is the _only_ such change, of course when the time comes reverting it won't be hard. Will it be? -- 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."