Author: branden Date: 2004-07-08 14:28:10 -0500 (Thu, 08 Jul 2004) New Revision: 1599
Modified: trunk/debian/TODO trunk/debian/local/FAQ.xhtml Log: Add item. Fabio, if you disagree with this for -7, please ratchet it down. Modified: trunk/debian/TODO =================================================================== --- trunk/debian/TODO 2004-07-08 19:01:45 UTC (rev 1598) +++ trunk/debian/TODO 2004-07-08 19:28:10 UTC (rev 1599) @@ -58,6 +58,7 @@ more careful about clobbering autodetected monitor sync ranges; study Jay Berkenbilt's feedback [BR] * Update XTerm to version #191. +* #255280: Apply patch to add libglide3 support for ia64 and amd64. * Shut up preprocessor warning at xc/config/cf/xfree86.cf:1031; test for "HasGlide3" symbol being defined before testing its value. * #253480: xdm: XDM fails if the user is over disk quota, but empty files can Modified: trunk/debian/local/FAQ.xhtml =================================================================== --- trunk/debian/local/FAQ.xhtml 2004-07-08 19:01:45 UTC (rev 1598) +++ trunk/debian/local/FAQ.xhtml 2004-07-08 19:28:10 UTC (rev 1599) @@ -101,8 +101,9 @@ of readable text, some characters appear as little gray boxes. Why?</a></li> <li><a href="#xservmemory">Why does the X server take up so much memory?</a></li> -<li><a href="#xtermwrongconfig">Why do the menus in xterm have the wrong font, - size, background color, or foregound color?</a></li> +<li><a href="#xtermwrongconfig">Why do the menus in <code + class="command">xterm</code> have the wrong font, size, background color, or + foregound color?</a></li> <li><a href="#upgrnonfreedriver">I just upgraded the X server and it doesn't work; also, I'm using Matrox's proprietary <code class="other">mga_hal</code> driver module or NVidia's proprietary <code class="other">nvidia</code> driver @@ -1925,13 +1926,15 @@ kernel sources which implement it is about the best manual I know of.</p> </blockquote> -<h3><a id="xtermwrongconfig">Why do the menus in xterm have the wrong font, -size, background color, or foregound color?</a></h3> +<h3><a id="xtermwrongconfig">Why do the menus in <code + class="command">xterm</code> have the wrong font, size, background color, or + foregound color?</a></h3> <p>Because, 99 times out of 100, you're not using X resources correctly.</p> -<p>If you have X resource specifications (say, in your $HOME/.Xresources file) -that look like this:</p> +<p>If you have X resource specifications (say, in your <code +class="filespec"><var>$HOME</var>/.Xresources</code> file) that look like +this:</p> <pre>XTerm*foreground: black XTerm*background: white @@ -1940,13 +1943,13 @@ <p>...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 <code -class="manpage">X(7x)</code> manual page.</p> +asterisk is a wildcard, not an ordinary separator. <code +class="command">xterm</code> 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 <code class="manpage">X(7x)</code> manual page.</p> -<p>If you want to set X resources for xterm that affect only its VT100 widget, -then you need to say so:</p> +<p>If you want to set X resources for <code class="command">xterm</code> that +affect only its VT100 widget, then you need to say so:</p> <pre>XTerm.VT100.background: white XTerm.VT100.foreground: black