Alexander Samad writes: > I have changed my .Xresources file to look like this > URxvt.font: a16 > > previously it was like > URxvt*font: a16
I'm not sure why you want to use the latter version, but here is the problem: I'm shipping a /etc/X11/app-defaults/URxvt that contains URxvt.font. A specific resource name, such as that one, overrides a less-specific wildcard that happens to match the same resource. So, yours ends up having no effect. I could simply put URxvt*font in the app-defaults, but I'd rather not have to then add an explanation of why such a specification is wrong and should not be copied into your personal resources even if it happens to work. Better alternatives would be: - I convince you that this is the wrong way to do it, and just add to the FAQ item - You convince me that the precedence rules in the parser are broken, and I change it/get upstream to change it Thoughts? (If you don't understand the problem with *font, try it with a client that uses both a custom text widget and toolkit widgets (in different places in the hierarchy), such as xterm or (older versions of) Emacs.) -- things change. [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
