retitle 254650 xterm: document utf8Fonts resource in NEWS.Debian or FAQ tag 254650 + moreinfo thanks Hi Thomas, Can you supply me with some text to provide here? I'm not completely sure I understand the problem, and until I do I don't know whether this is more of a FAQ issue and/or a NEWS.Debian issue. I'm thinking of something structured like: If you <...>, then you need to <... utf8Fonts ...> instead of <...> or undesirable behavior <...> will result. It *sounds* like the kind of hyperaggressive wildcard problem that results in the following: http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ.xhtml#xtermwrongconfig Why do the menus in xterm have the wrong font, size, background color, or foregound color? Because, 99 times out of 100, you're not using X resources correctly. If you have X resource specifications (say, in your $HOME/.Xresources file) that look like this: XTerm*foreground: black XTerm*background: white XTerm*geometry: 200x55-0+20 XTerm*font: 10x20 ...then be aware that you are, in fact, telling the menus, not just the VT100 widget, to use the 10x20 font with white-on-black text. That asterisk is a wildcard, not an ordinary separator. XTerm is doing exactly what you are telling it to do. If you find X resources confusing, don't use them, or read the "RESOURCES" section of the X(7x) manual page. If you want to set X resources for xterm that affect only its VT100 widget, then you need to say so: XTerm.VT100.background: white XTerm.VT100.foreground: black XTerm.VT100.font: 10x20 XTerm.VT100.geometry: 200x55-0+20 -- G. Branden Robinson | The first thing the communists do Debian GNU/Linux | when they take over a country is to branden@debian.org | outlaw cockfighting. http://people.debian.org/~branden/ | -- Oklahoma State Senator John Monks
Attachment:
signature.asc
Description: Digital signature