[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

X Strike Force XFree86 SVN commit: r1542 - in trunk/debian: . local

Author: branden
Date: 2004-06-15 16:33:52 -0500 (Tue, 15 Jun 2004)
New Revision: 1542

Update XTerm FAQ to latest version from Thomas Dickey's website.

Modified: trunk/debian/CHANGESETS
--- trunk/debian/CHANGESETS	2004-06-15 21:28:54 UTC (rev 1541)
+++ trunk/debian/CHANGESETS	2004-06-15 21:33:52 UTC (rev 1542)
@@ -173,4 +173,7 @@
 to include (X)HTML form of FAQ document.
+Update XTerm FAQ to latest version from Thomas Dickey's website.
+    1542
 vim:set ai et sts=4 sw=4 tw=80:

Modified: trunk/debian/changelog
--- trunk/debian/changelog	2004-06-15 21:28:54 UTC (rev 1541)
+++ trunk/debian/changelog	2004-06-15 21:33:52 UTC (rev 1542)
@@ -11,8 +11,10 @@
     Add build-dependency on lynx.  Update xfree-common's doc-base information
     to include (X)HTML form of FAQ document.
- -- Branden Robinson <branden@debian.org>  Tue, 15 Jun 2004 16:06:57 -0500
+  * Update XTerm FAQ to latest version from Thomas Dickey's website.
+ -- Branden Robinson <branden@debian.org>  Tue, 15 Jun 2004 16:31:22 -0500
 xfree86 (4.3.0.dfsg.1-4+SVN) unstable; urgency=low
   Changes by Branden Robinson:

Modified: trunk/debian/local/xterm.faq.html
--- trunk/debian/local/xterm.faq.html	2004-06-15 21:28:54 UTC (rev 1541)
+++ trunk/debian/local/xterm.faq.html	2004-06-15 21:33:52 UTC (rev 1542)
@@ -1,15 +1,16 @@
-  $Id: xterm.faq.html,v 1.77 2003/01/12 18:40:57 tom Exp $
+  $Id: xterm.faq.html,v 1.80 2004/04/09 00:41:26 tom Exp $
 <TITLE>XTERM - Frequently Asked Questions (FAQ)</TITLE>
 <LINK REV=MADE HREF="mailto:dickey@invisible-island.net";>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-Copyright 1997-2002,2003 by Thomas E. Dickey
+Copyright 1997-2003,2004 by Thomas E. Dickey
@@ -43,7 +44,8 @@
 A lot of people, cited at the bottom of the manual page wrote
 the original xterm program, maintained by the X Consortium
-(now part of the Open Group).
+(later part of the Open Group - I'm well aware of the distinction,
+but am citing when the work was done, not who the current owner may be).
 There is no changelog, and it is not clear who did what.
 Email from Jim Gettys provides some background:
@@ -132,12 +134,12 @@
 <LI>AIX 3.2.5 (cc)
 <LI>Digital Unix 3.2, 4.0 (cc)
-<LI>FreeBSD 2.2.6 (gcc 2.8)
+<LI>FreeBSD 2.2.6 to 5.1 (gcc 2.8)
 <LI>HP-UX 9.05 (gcc 2.7.2)
 <LI>IRIX 5.2, 6.2 (cc, gcc 2.7.2, gcc 2.8)
-<LI>Linux 2.0.0 to 2.4.9 (gcc 2.7.2 to 3.0)
+<LI>Linux 2.0.0 to 2.4.22 (gcc 2.7.2 to 3.3)
 <LI>SCO OpenServer 5 (cc, gcc).
-<LI>Solaris 2.4, 2.5, 2.5.1, 2.6 (cc, gcc 2.7.2)
+<LI>Solaris 2.4, 2.5, 2.5.1, 2.6, 7, 8 (cc, gcc 2.7.2)
 <LI>SunOS 4.1.1, 4.1.3 (gcc 2.7.2)
@@ -173,7 +175,7 @@
 <LI><A HREF="#bug_rxvt">rxvt</A>
 <LI><A HREF="#bug_xgterm">xgterm</A>
 <LI><A HREF="#bug_xiterm">xiterm</A>
-<LI><A HREF="#bug_xterm">xterm</A> (from X Consortium)
+<LI><A HREF="#bug_xterm_r6">xterm</A> (from X Consortium)
 (I am aware of a few others, such as
 <STRONG>xcterm</STRONG>, but have not seen
@@ -244,7 +246,7 @@
 In fact XFree86 xterm does.  Logging was dropped from X Consortium xterm
 during X11R5 due to security concerns.  Those were addressed, but logging
 was not reinstated
-(in fact there is a related <a href="#bug_xterm">bug</a> in xterm).
+(in fact there is a related <a href="#bug_xterm_r6">bug</a> in xterm).
 Some people prefer this, because it is convenient:
 you can start and stop logging a popup menu entry.
@@ -333,10 +335,10 @@
 with the corresponding resources:
-	XTerm*VT100.Translations: #override \n\
+	XTerm*VT100.translations: #override \n\
 		&lt;Key&gt;Home: string(0x1b) string("[3~") \n \
 		&lt;Key&gt;End: string(0x1b) string("[4~") \n
-	vt220*VT100.Translations: #override \n\
+	vt220*VT100.translations: #override \n\
 	~Shift	&lt;Key&gt;F1: string(0x1b) string("OP") \n \
 	~Shift	&lt;Key&gt;F2: string(0x1b) string("OQ") \n \
 	~Shift	&lt;Key&gt;F3: string(0x1b) string("OR") \n \
@@ -876,11 +878,6 @@
 GNOME Terminal,
 and XFree86 xterm
 (from mid 1999, <a href="xterm.log.html#xterm_107">patch 107</a>).
-By default, XFree86 xterm's blinking cursor is not enabled because there
-is a minor problem with it: when writing large amounts of text to the
-screen, it may pause until you press a key (even the shift key).
-For normal use it works well.
 <H1><A NAME="frequent_problems">Frequent problems</A></H1>
@@ -1043,7 +1040,7 @@
 pageup and pagedown keys talk to the xterm's scrollbar instead of your
 They did the same thing for the home and end keys, thereby obscuring
-a bug in <A NAME="bug_xterm">xterm</A>.
+a bug in <A HREF="#bug_xterm_r6">xterm</A>.
 You can override this by specifying your own translations in your resource
@@ -1054,7 +1051,7 @@
 as a guide.
 The relevant section of the app-default file looks like
-	*VT100.Translations:    #override \
+	*VT100.translations:    #override \
 		@Num_Lock&lt;Key&gt;KP_0: string(0)\n\
 		@Num_Lock&lt;Key&gt;KP_1: string(1)\n\
 		@Num_Lock&lt;Key&gt;KP_2: string(2)\n\
@@ -1083,7 +1080,7 @@
 For example, a more-specific pattern for the resource name lets you override:
-	XTerm.VT100.Translations:       #override \n\
+	XTerm.VT100.translations:       #override \n\
 		~Shift&lt;Key&gt;Home:  string(\033[1~)\n\
 		~Shift&lt;Key&gt;End:   string(\033[4~)\n\
 		~Shift&lt;Key&gt;Prior: string(\033[5~)\n\
@@ -1098,7 +1095,7 @@
 <H2><A NAME="xterm_pc_style">Why can't I use the home/end keys?</A></H2>
 This is a long story,
-unless you are referring to X Consortium <A NAME="bug_xterm">xterm</A>.
+unless you are referring to X Consortium <A HREF="#bug_xterm_r6">xterm</A>.
 That program is simply broken in this respect.
 At the beginning, when the home/end keys were fixed for XFree86 xterm
@@ -1882,7 +1879,7 @@
 file whose translations match widgets that do not support them.
 For example, this
-		XTerm*Translations:     #override\n\
+		XTerm*translations:     #override\n\
 			&lt;Leave&gt;, ~Ctrl ~Meta &lt;Btn2Up&gt;: ignore()\n\
 			~Shift &lt;Key&gt;KP_8: scroll-back(1,line)\n\
 			~Shift &lt;Key&gt;KP_2: scroll-forw(1,line)\n\
@@ -1953,7 +1950,7 @@
 <LI>does not implement the autorepeat feature of VTxxx terminals.
-<H3><A NAME="bug_xterm">X11R6.3 XTERM</A></H3>
+<H3><A NAME="bug_xterm_r6">X11R6.3 XTERM</A></H3>
 The X Consortium version of xterm (and versions based on it) has
 additional bugs not in XFree86 xterm:
@@ -1971,6 +1968,18 @@
 does not check the event class before attempting to use events.
 (These bugs are also present in the X11R5 version).
+Update 2004/04/08:
+Complicating this discussion is the recently-released "X.Org" xterm.
+That is the XFree86 xterm from XFree86 CVS
+with all visible "xfree86" strings changed to "X.Org" or "xorg",
+depending on the use.
+For example the "xterm-xfree86" terminfo entry becomes "xterm-xorg".
+The change history for the related CVS for X.Org shows this.
+Similarly, the release notes for X11R6.7 include my notes for XFree86 4.4.
+It is of course too soon to see the overall impact of this,
+so I'll update this FAQ as I find it necessary.
 <H3><A NAME="bug_color_xterm">COLOR_XTERM</A>
 <A HREF="ftp://www.x.org/contrib/applications/color_xterm-beta1.tar.gz";>download</A></H3>
@@ -2091,8 +2100,8 @@
 This is based on the XFree86 source.
 <H3><A NAME="bug_konsole">KONSOLE</A>
-<a href="www.kde.org/">link</a></H3>
-More than just a rewrite of <a href="bug_kvt">kvt</a> into C++.
+<a href="http://www.kde.org/";>link</a></H3>
+More than just a rewrite of <a href="#bug_kvt">kvt</a> into C++.
 But there are several incompatibilities between konsole 1.0.2 (late 2001)
 and xterm:
@@ -2111,7 +2120,7 @@
       than a year before development of konsole began).
   <li>konsole implements several features from XFree86 xterm, but some are
       done incorrectly.
-      In particular, the <a href="xterm_tite">private setmode 1049</a>
+      In particular, the <a href="#xterm_tite">private setmode 1049</a>
       does not save and restore the cursor,
       causing the cursor to be in unexpected locations
       after exiting a fullscreen application such as vi.
@@ -2130,7 +2139,7 @@
 There is a variation of xvt (ancestor of rxvt) originally known as
 <A NAME="bug_kvt">kvt</A>
 bundled with
-<a href="www.kde.org/">KDE</a>
+<a href="http://www.kde.org/";>KDE</a>
 which may be referred to as
 "kterm", but I do not find it interesting,
 other than to comment that it was a poor choice of name.
@@ -2224,7 +2233,7 @@
 accounts for about 25kb of the code.
 The toolkit-style configurability glibly referenced is the ability to
 redefine keys on the keyboard without recompiling the program,
-i.e., the <a href="how2_fkeys">translations</a> resource.
+i.e., the <a href="#how2_fkeys">translations</a> resource.
 The toolkit-style configurability
 accounts for about 300kb, which does add up if you happen to be
 running 50 xterm processes (i.e., about 10Mb).
@@ -2341,18 +2350,6 @@
 <H1><A NAME="future_work">Ongoing/future work</A></H1>
-<LI>double-high/double-wide characters
-<P>I have implemented double size characters in stages:
-<li>Like Kermit, XFree86 xterm can show normal characters spaced at the proper intervals.
-<li>If your font server cooperates (e.g., X11R6), you can display many fixed
-fonts in double-size, though not all.
-<li>XFree86 xterm can also generate its own line-drawing characters,
-which normally are missing from fixed fonts except for those that
-were designed for xterm.
-<li>Other than the limitations which the font server may impose,
-the double size characters are drawn properly.
 <LI>soft (downloadable) fonts
 <LI>search scrollback
 It would be nice to be able to search the scrollback buffer.
@@ -2372,13 +2369,8 @@
 In turn, that works well enough except with XFree86 4.x:
 the Xaw library geometry management is broken.
 (Other implementations of the Athena widgets work well enough).
-<LI>blinking text.
-Just for completeness (though no one seems to want this feature).
-<LI>Double-width font support for UTF-8 mode (for CJK users)
 <LI>popup window that shows hex code for content of a character cell
 and hexadecimal keyboard entry for all Unicode characters (ISO 14755)
-<LI>UTF-8 combining character support (simple glyph overstriking only)
 <LI>correct cut&amp;paste of TAB character

Reply to: