Stephen and Jan, thank you for the discussion. I understand the issues better
than I did before.
I agree with Stephen that there seems to be a deeper problem here than the one
that I am trying to fix. I need to think about this some more. If nothing
else, I'd like to see some consensus about "how things ought to be".
Jan> No but Paul has real problems that need to be fixed. His setup might
Jan> be rare now but it might not be in the future.
My problems are annoying, but cosmetic. Maybe this isn't an issue that should
be addressed in 21.0. Perhaps after 21.0 is released and all of the CYGWIN+X
users[1] start screaming bloody murder, then it can be fixed for 21.1.
Jan> This does seem the right way to fix that. You have settings that are
Jan> valid only for a particular type of device so you add a tag set to
Jan> reflect that. The current code is just a cop out.
The current code is broken, definitely. And if tag sets do refer to devices,
then I think that my patch is ok. But if tag sets involve MULE ... <shudder>
Boy, this is one hell of a way to get my feet wet with XEmacs development,
huh? Custom, Windows, specifiers, _and_ MULE!
[1] Let's see, there's me ... Andy, I think ... and ... umm ...