Bug#447519: xterm: [UXTerm] doesn't support *XTerm class in ~/.Xresources
reassign 447519 x11-common
retitle 447519 x11-common: [Xresources] doesn't support '*' as a 'common' wildcard
found 447519 1:7.3+2
thanks
Hi Thomas!
Since the problem isn't in xterm, but in Xt resources, I reassigned
the bug to x11-common (because it's the package that ships
/etc/X11/Xresources).
On Tue, 23 Oct 2007 22:15:38 +0200, Thomas Dickey wrote:
> On Tue, Oct 23, 2007 at 07:42:21PM +0200, Luca Capello wrote:
>> 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".
>
> Wildcards in Xt resources aren't supposed to do that (oddly enough).
> They replace whole leaf-names rather than parts of them. The resource
> syntax is documented in the X manpage (at the moment I'm on Solaris,
> and know the the Linux manpage is named different...). Here's the
> text, for reference:
Thank you for the explanation and I agree that it's oddly enough that
wildcards behave differently in Xt resources....
> I usually do this a different way, setting
> $XAPPLRESDIR
> to my
> $HOME/app-defaults
> (and putting individual resource files there).
Again, thank you for the hint, but I don't have a lot of Xt resources
and I prefer to set them in one single file.
I haven't closed this bug yet because I don't really know how to
proceed: either we just close this bug as a not-a-bug or we leave this
bug opened as a wishlist, tagging it upstream, too. In the latter
case, since I think it's quite difficult that Xt resources will be
changed to use 'common' wildcards, the bug is eligible for a wontfix
tag, too.
Thx, bye,
Gismo / Luca
Reply to: