Hi Thomas! On Tue, 23 Oct 2007 17:47:00 +0200, Thomas Dickey wrote: > On Sun, Oct 21, 2007 at 11:40:11PM +0200, Luca Capello wrote: >> I'm not sure this is really a bug, but I cannot find anything in >> the documentation. In case it's there, can anyone point me at it, >> please? >> >> Basically, I'd like to define UXTerm resources in the *XTerm form >> (which is perfectly valid for xterm itself), in order to avoid >> resource duplications. As I wrote, it seems that xterm supports >> *XTerm, while uxterm no. > > The uxterm script sets the class to "UXTerm" so that there are no > conflicts in resource intent/interpretation between the two uses.
I'm aware of that and indeed this is a reason I started with "I'm not sure this is really a bug". If the "problem" is not clear, here my second try: I usually quite exclusively uxterm and thus I could specify UXTerm resources as UXTerm. However, sometime I start an xterm and, obviously, I don't have my UXTerm settings. Since resources specified as *XTerm are correctly read by xterm, I assumed that '*' is a wildcard, which stands for "all", thus "*XTerm" means "every class which ends in XTerm". If the latter is right, this should be the case for UXTerm, too. Since it's not the case, this is a bug. However, if I'm wrong, I'll change the severity of this bug as 'wishlist' ;-) Thx, bye, Gismo / Luca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]