"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
It's removing specifications with tags on them (specifically, it
once again nuking _all_ '(mule-tags) fonts on 'default). This is in
That is strange. The new specifier tags based mechanism is supposed to
touch (create/remove) only those specification with a "custom" tag.
Could you find out where this is happening?
IMHO, Custom should not be touching _anything_ it doesn't put on
specifier itself. But that's arguable.
It is not arguable that it is evil for Custom to touch any
specification with a non-null tagset that doesn't include Custom's
signature. If I put a specification with a tag on it on a specifier,
Custom had better leave it alone.
The tag based mechanism should do neither of these.