xterm: Changes to 'debian-unstable'
MANIFEST | 2
Makefile.in | 21 -
charproc.c | 30 +
data.h | 7
debian/changelog | 9
debian/local/xterm.faq.html | 777 ++++++++++++++++++++--------------------
debian/upstream/signing-key.asc | 24 +
debian/watch | 2
main.c | 26 -
minstall.in | 10
misc.c | 174 +++++---
package/debian/changelog | 6
package/debian/control | 2
package/debian/rules | 2
package/freebsd/Makefile | 2
package/xterm.spec | 39 +-
ptyx.h | 26 +
trace.c | 7
version.h | 6
vttests/256colors.pl | 13
vttests/256colors2.pl | 13
vttests/88colors.pl | 11
vttests/88colors2.pl | 13
vttests/dynamic.pl | 7
vttests/paste64.pl | 8
vttests/query-color.pl | 7
vttests/query-fonts.pl | 7
vttests/resize.pl | 28 +
vttests/tcapquery.pl | 7
xterm.h | 4
xterm.log.html | 53 ++
xterm.man | 53 ++
32 files changed, 852 insertions(+), 544 deletions(-)
New commits:
commit aec7c9ef6b87b5fce4de8a2b53d91623a1045e02
Author: Sven Joachim <svenjoac@gmx.de>
Date: Mon Mar 3 19:07:23 2014 +0100
Update copy of XTerm FAQ to revision 1.278 (dated 2014/02/24)
The paragraph that mentions /usr/lib/X11/app-defaults/XTerm has been
rewritten to clarify that it applies to Solaris only.
diff --git a/debian/changelog b/debian/changelog
index 80e5f94..a7bbeff 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
xterm (302-1) UNRELEASED; urgency=low
* New upstream release.
+ * Update copy of XTerm FAQ to revision 1.278 (dated 2014/02/24)
+ (Closes: #737692).
* Check GPG signature of upstream tarballs in the watch file.
-- Sven Joachim <svenjoac@gmx.de> Mon, 03 Mar 2014 18:39:43 +0100
diff --git a/debian/local/xterm.faq.html b/debian/local/xterm.faq.html
index 312fa10..026dfe1 100644
--- a/debian/local/xterm.faq.html
+++ b/debian/local/xterm.faq.html
@@ -1,6 +1,6 @@
<!--
*****************************************************************************
- * Copyright 1997-2012,2013 by Thomas E. Dickey *
+ * Copyright 1997-2013,2014 by Thomas E. Dickey *
* All Rights Reserved. *
* *
* Permission to use, copy, modify, and distribute this software and its *
@@ -19,8 +19,7 @@
* ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF *
* OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. *
*****************************************************************************
- $XTermId: xterm.faq.html,v 1.259 2013/11/25 10:22:56 tom Exp $
- <base href="http://invisible-island.net/xterm/";>
+ $XTermId: xterm.faq.html,v 1.278 2014/02/24 22:32:04 tom Exp $
-->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
@@ -33,6 +32,10 @@
<link rev="MADE" href="mailto:dickey@invisible-island.net";>
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii">
+ <meta name="keywords" content=
+ "xterm, terminal, vt220, vt420, 256-colors, UTF-8">
+ <meta name="description" content=
+ "xterm is the standard terminal emulator for the X Window System. This page gives some background and pointers to xterm resources.">
<link rel="SHORTCUT ICON" href="/img/icons/xterm.ico" type=
"image/x-icon">
<link rel="stylesheet" href="/css/simplestyle.css" type=
@@ -42,65 +45,65 @@
<link rel="stylesheet" href="/css/xterm-icons.css" type=
"text/css">
<style type="text/css">
-@import "/css/simplenav15.css" all;
+@import "/css/simplenavXX.css" all;
</style>
</head>
<body>
<hr>
- <p><a href="../">http://invisible-island.net/</a><a href=
+ <p><a href="/">http://invisible-island.net/</a><a href=
"./">xterm/</a><br>
- Copyright © 1997-2012,2013 by Thomas E. Dickey</p>
+ Copyright © 1997-2013,2014 by Thomas E. Dickey</p>
<hr>
- <p><a href="xterm.faq.html">Here</a> is the latest version of
- this file.</p>
+ <p><a href=
+ "http://invisible-island.net/xterm/xterm.faq.html";>Here</a> is
+ the latest version of this file.</p>
+
+ <h1 class="no-header">XTerm – Frequently Asked Questions
+ (FAQ)</h1>
<div class="nav">
<ul>
- <li><a href="xterm.faq.html">(top)</a></li>
+ <li class="nav-top"><a href=
+ "/xterm/xterm.faq.html">(top)</a></li>
- <li><a href="xterm.faq.html#what_is_it">What is
+ <li><a href="#what_is_it">What is
<strong>XTerm</strong>?</a></li>
- <li><a href="xterm.faq.html#who_did_it">Who wrote
+ <li><a href="#who_did_it">Who wrote
<strong>XTerm</strong>?</a></li>
- <li><a href="xterm.faq.html#what_is_vt220">What is a
- VT220?</a></li>
+ <li><a href="#what_is_vt220">What is a VT220?</a></li>
- <li><a href="xterm.faq.html#what_platforms">What platforms
- does it run on?</a></li>
+ <li><a href="#what_platforms">What platforms does it run
+ on?</a></li>
- <li><a href="xterm.faq.html#latest_version">What is the
- latest version?</a></li>
+ <li><a href="#latest_version">What is the latest
+ version?</a></li>
- <li><a href="xterm.faq.html#other_versions">What versions are
+ <li><a href="#other_versions">What versions are
available?</a></li>
- <li><a href="xterm.faq.html#compare_versions">Comparing
- versions, by counting controls</a></li>
+ <li><a href="#compare_versions">Comparing versions, by
+ counting controls</a></li>
- <li><a href="xterm.faq.html#how_do_i">How do I ...</a></li>
+ <li><a href="#how_do_i">How do I ...</a></li>
- <li><a href="xterm.faq.html#frequent_problems">Frequent
- problems</a></li>
+ <li><a href="#frequent_problems">Frequent problems</a></li>
- <li><a href="xterm.faq.html#known_bugs">Known Bugs in
+ <li><a href="#known_bugs">Known Bugs in
<strong>XTerm</strong> and Look–alikes</a></li>
- <li><a href="xterm.faq.html#building_it">How do I build
+ <li><a href="#building_it">How do I build
<strong>XTerm</strong>?</a></li>
- <li><a href="xterm.faq.html#report_bugs">How do I report
- bugs?</a></li>
+ <li><a href="#report_bugs">How do I report bugs?</a></li>
- <li><a href="xterm.faq.html#more_info">Additional
- Information</a></li>
+ <li><a href="#more_info">Additional Information</a></li>
- <li><a href="xterm.faq.html#future_work">Ongoing/future
- work</a></li>
+ <li><a href="#future_work">Ongoing/future work</a></li>
</ul>
</div>
@@ -130,8 +133,8 @@
it.</p>
<p>As a stylistic convention, the capitalized form is
- "<em>XTerm</em>", which corresponds to the X resource class name.
- Similarly, <em>uxterm</em> becomes "<em>UXTerm</em>".</p>
+ <em>"XTerm"</em>, which corresponds to the X resource class name.
+ Similarly, <em>uxterm</em> becomes <em>"UXTerm"</em>.</p>
<h2 id="who_did_it-id"><a name="who_did_it" id="who_did_it">Who
wrote <strong>XTerm</strong>?</a></h2>
@@ -233,15 +236,15 @@
Involvement</a></h3>
<p>My involvement with <strong>xterm</strong> through XFree86
- began at the <a href="xterm.html#history">end of 1995</a>. This
- website has been "here" since 2001/6/5, replacing my ClarkNet
- page. I started the ClarkNet page 1996/12/31, as a followup to
- the <a href=
- "http://invisible-island.net/ncurses/ncurses-license.html#patch_961224";>
- release of ncurses 4.0</a>) which featured xterm as one of the 16
- programs I was involved with. From the outset, the page provided
- a link to a snapshot of the current source. Copies of patches
- which I sent to XFree86 were available on the ftp area.</p>
+ began at the <a href="/xterm/xterm.html#history">end of 1995</a>.
+ This website has been "here" since 2001/6/5, replacing my
+ ClarkNet page. I started the ClarkNet page 1996/12/31, as a
+ followup to the <a href=
+ "/ncurses/ncurses-license.html#patch_961224">release of ncurses
+ 4.0</a>) which featured xterm as one of the 16 programs I was
+ involved with. From the outset, the page provided a link to a
+ snapshot of the current source. Copies of patches which I sent to
+ XFree86 were available on the ftp area.</p>
<p>XFree86 had its sources in CVS, but (like others in that era),
were not directly visible to random developers. That came later.
@@ -250,16 +253,14 @@
updating them with patches from the XFree86 mailing list.</p>
<p>Like the other programs that I worked on with others (<a href=
- "http://invisible-island.net/vile/vile.html";>vile</a>, <a href=
- "http://invisible-island.net/tin/tin.html";>tin</a>, <a href=
- "http://invisible-island.net/lynx/lynx.html";>lynx</a>), I set up
- an RCS archive to track my changes locally before sending patches
- to the development list. As the XFree86 developers issued new
- patches, I would re-synchronize my archive. Later, XFree86
- provided CVS (initially readonly). I was granted commit
- privileges on this <a href=
- "http://invisible-island.net/ansification/ansify-xfs-cve.html#xfree86_work";>
- in November 2000</a>.</p>
+ "/vile/vile.html">vile</a>, <a href="/tin/tin.html">tin</a>,
+ <a href="/lynx/lynx.html">lynx</a>), I set up an RCS archive to
+ track my changes locally before sending patches to the
+ development list. As the XFree86 developers issued new patches, I
+ would re-synchronize my archive. Later, XFree86 provided CVS
+ (initially readonly). I was granted commit privileges on this
+ <a href="/ansification/ansify-xfs-cve.html#xfree86_work">in
+ November 2000</a>.</p>
<p>Throughout this period, my work on <strong>xterm</strong> was
released as part of XFree86. It was rare for a separate package
@@ -286,7 +287,7 @@
"xterm.log.html#xterm_205">patch #205</a>.</li>
<li>The Debian package for xterm began in January 6, 2006 with
- <a href="xterm.log.html#xterm_204">patch #204</a>.</li>
+ <a href="/xterm/xterm.log.html#xterm_204">patch #204</a>.</li>
</ul>
<p>Given that context (sources distributed via XFree86 CVS,
@@ -301,11 +302,11 @@
"xterm.faq.html#xterm-xorg">fork</a>" (sic) of Xorg in 2004,
I continued to commit changes for xterm in <a href=
"http://cvsweb.xfree86.org/cvsweb/xc/programs/xterm/";>XFree86
- CVS</a> until <a href="xterm.log.html#xterm_216">patch #216</a>
- in mid-2006. I stopped at that point because it was not possible
- to incorporate changes into xterm which were not sent to me
- first. I still send patch announcements to both the XFree86 and
- Xorg mailing lists, of course.</p>
+ CVS</a> until <a href="/xterm/xterm.log.html#xterm_216">patch
+ #216</a> in mid-2006. I stopped at that point because it was not
+ possible to incorporate changes into xterm which were not sent to
+ me first. I still send patch announcements to both the XFree86
+ and Xorg mailing lists, of course.</p>
<h3 id="forward_history-id"><a name="forward_history" id=
"forward_history">Focus of this FAQ</a></h3>
@@ -331,7 +332,7 @@
function keys. My keyboard has 12 function keys.</li>
<li>VT100s do not do <a href=
- "../ncurses/ncurses.faq.html">color</a>.</li>
+ "/ncurses/ncurses.faq.html">color</a>.</li>
</ul>
<p>Initially, I was only interested in making colors workable for
@@ -372,8 +373,8 @@
implement in shell scripts than <code>ESC \</code>.</li>
</ul>
- <p>I revised that area <a href="xterm.log.html#xterm_24">starting
- in 1996</a>,</p>
+ <p>I revised that area <a href=
+ "/xterm/xterm.log.html#xterm_24">starting in 1996</a>,</p>
<ul>
<li>first to use xterm's state table for handling the input,
@@ -389,7 +390,7 @@
characters. That is essentially what a real terminal does. Other
"xterm" terminal emulators typically do not do this, which makes
them not do well with <a href=
- "../vttest/vttest.html">vttest</a>.</p>
+ "/vttest/vttest.html">vttest</a>.</p>
<h2 id="what_platforms-id"><a name="what_platforms" id=
"what_platforms">What platforms does it run on?</a></h2>
@@ -435,9 +436,8 @@
"ftp://invisible-island.net/xterm/xterm.tar.gz";>current source
(ftp)</a></li>
- <li><a href=
- "http://invisible-island.net/datafiles/release/xterm.tar.gz";>current
- source (http)</a></li>
+ <li><a href="/datafiles/release/xterm.tar.gz">current source
+ (http)</a></li>
</ul>
<h2 id="other_versions-id"><a name="other_versions" id=
@@ -447,73 +447,66 @@
source. These include</p>
<ul>
- <li><a href="xterm.faq.html#bug_ansi_xterm">ansi_xterm</a></li>
+ <li><a href="#bug_ansi_xterm">ansi_xterm</a></li>
<li><a href=
"xterm.faq.html#bug_color_xterm">color_xterm</a></li>
- <li><a href="xterm.faq.html#bug_cxterm">cxterm</a>
- (Chinese)</li>
+ <li><a href="#bug_cxterm">cxterm</a> (Chinese)</li>
- <li><a href="xterm.faq.html#bug_hanterm">hanterm</a>
- (Korean)</li>
+ <li><a href="#bug_hanterm">hanterm</a> (Korean)</li>
- <li><a href="xterm.faq.html#bug_mxterm">mxterm</a></li>
+ <li><a href="#bug_mxterm">mxterm</a></li>
- <li><a href="xterm.faq.html#bug_nxterm">nxterm</a></li>
+ <li><a href="#bug_nxterm">nxterm</a></li>
- <li><a href="xterm.faq.html#bug_kterm">kterm</a>
- (Japanese)</li>
+ <li><a href="#bug_kterm">kterm</a> (Japanese)</li>
- <li><a href="xterm.faq.html#bug_xterm_r6">xterm</a> (from X
- Consortium)</li>
+ <li><a href="#bug_xterm_r6">xterm</a> (from X Consortium)</li>
</ul>
<p>There are similar programs not based on xterm's source, which
are compatible to different degrees. These include</p>
<ul>
- <li><a href="xterm.faq.html#bug_dtterm">dtterm</a></li>
+ <li><a href="#bug_dtterm">dtterm</a></li>
- <li><a href="xterm.faq.html#bug_emu">emu</a> (from X
- Consortium)</li>
+ <li><a href="#bug_emu">emu</a> (from X Consortium)</li>
- <li><a href="xterm.faq.html#bug_eterm">Eterm</a></li>
+ <li><a href="#bug_eterm">Eterm</a></li>
- <li><a href="xterm.faq.html#bug_gnometerm">GNOME
- Terminal</a></li>
+ <li><a href="#bug_gnometerm">GNOME Terminal</a></li>
- <li><a href="xterm.faq.html#bug_multignome">Multi GNOME
- Terminal (MGT)</a></li>
+ <li><a href="#bug_multignome">Multi GNOME Terminal
+ (MGT)</a></li>
- <li><a href="xterm.faq.html#bug_mterm">mterm</a></li>
+ <li><a href="#bug_mterm">mterm</a></li>
- <li><a href="xterm.faq.html#bug_konsole">konsole</a></li>
+ <li><a href="#bug_konsole">konsole</a></li>
- <li><a href="xterm.faq.html#bug_mlterm">mlterm</a> (Multi
- Lingual)</li>
+ <li><a href="#bug_mlterm">mlterm</a> (Multi Lingual)</li>
- <li><a href="xterm.faq.html#bug_osso_xterm">osso-xterm</a></li>
+ <li><a href="#bug_osso_xterm">osso-xterm</a></li>
- <li><a href="xterm.faq.html#bug_roxterm">roxterm</a></li>
+ <li><a href="#bug_roxterm">roxterm</a></li>
- <li><a href="xterm.faq.html#bug_rxvt">rxvt</a></li>
+ <li><a href="#bug_rxvt">rxvt</a></li>
- <li><a href="xterm.faq.html#bug_st">st</a></li>
+ <li><a href="#bug_st">st</a></li>
- <li><a href="xterm.faq.html#bug_xfce_term">xfce-term</a></li>
+ <li><a href="#bug_xfce_term">xfce-term</a></li>
- <li><a href="xterm.faq.html#bug_xgterm">xgterm</a></li>
+ <li><a href="#bug_xgterm">xgterm</a></li>
- <li><a href="xterm.faq.html#bug_xiterm">xiterm</a></li>
+ <li><a href="#bug_xiterm">xiterm</a></li>
</ul>
- <p>Some of these use the <a href="xterm.faq.html#vte_widget">VTE
- widget</a>. Since that supplies most of the terminal emulation,
- the remaining differences between programs using VTE tend to be
- at the level of the window manager (menus, borders, etc.). Other
- (older) programs which are based on reusable widgets include
- <a href="xterm.faq.html#bug_dtterm">dtterm</a> and <a href=
+ <p>Some of these use the <a href="#vte_widget">VTE widget</a>.
+ Since that supplies most of the terminal emulation, the remaining
+ differences between programs using VTE tend to be at the level of
+ the window manager (menus, borders, etc.). Other (older) programs
+ which are based on reusable widgets include <a href=
+ "#bug_dtterm">dtterm</a> and <a href=
"xterm.faq.html#bug_emu">emu</a>.</p>
<p>(I am aware of a few others, such as <strong>xcterm</strong>,
@@ -527,7 +520,7 @@
<li>PuTTY does this. But its wrapping behavior is incompatible
with xterm (and any vt100 emulator). You can see this in the
first menu entry for <a href=
- "../vttest/vttest.html">vttest</a>.</li>
+ "/vttest/vttest.html">vttest</a>.</li>
<li>VTE does this. But consider the list of problems with
<a href=
@@ -549,7 +542,7 @@
which are known to differ markedly from xterm have their own
terminal descriptions in ncurses, to which TERM should be set.
Otherwise, bug-reports are misdirected to <a href=
- "../ncurses/ncurses.html#download_database">ncurses</a> which
+ "/ncurses/ncurses.html#download_database">ncurses</a> which
should have been addressed by the respective developers of these
programs. These include</p>
@@ -1124,7 +1117,7 @@
programs change far more slowly, adding only one to konsole. Even
for cases where they implement a function, it may not work
properly (see for example the screenshot of VTE in the <a href=
- "../vttest/vttest-nrcs.html">vttest NRCS</a> examples).</p>
+ "/vttest/vttest-nrcs.html">vttest NRCS</a> examples).</p>
<p>In summary, none of the other terminal emulators emulates
"most" of xterm. Instead, they implement the most commonly-used
@@ -1137,20 +1130,18 @@
of this, after all):</p>
<ul>
- <li><a href="xterm.faq.html#how2_fsize">How do I change the
- font size?</a></li>
+ <li><a href="#how2_fsize">How do I change the font
+ size?</a></li>
- <li><a href="xterm.faq.html#how2_print">How do I print the
- screen?</a></li>
+ <li><a href="#how2_print">How do I print the screen?</a></li>
- <li><a href="xterm.faq.html#how2_fkeys">How do I set up
- function keys?</a></li>
+ <li><a href="#how2_fkeys">How do I set up function
+ keys?</a></li>
- <li><a href="xterm.faq.html#how2_title">How do I set the
- title?</a></li>
+ <li><a href="#how2_title">How do I set the title?</a></li>
- <li><a href="xterm.faq.html#how2_blink">How do I make the
- cursor blink?</a></li>
+ <li><a href="#how2_blink">How do I make the cursor
+ blink?</a></li>
</ul>
<h3 id="how2_fsize-id"><a name="how2_fsize" id="how2_fsize">How
@@ -1159,7 +1150,7 @@
<p><strong>XTerm</strong> uses fonts given as resource settings.
You can switch between these fonts at runtime, using a menu. This
is documented in the manpage, in the <a href=
- "manpage/xterm.html#MENUS">MENUS</a> section.</p>
+ "/xterm/manpage/xterm.html#MENUS">MENUS</a> section.</p>
<p>X Consortium xterm provides popup menus, by pressing the
control key together with the mouse button. Control right mouse
@@ -1199,9 +1190,9 @@
logging to a file. In fact modern 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="xterm.faq.html#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. However</p>
+ 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. However</p>
<ul>
<li>Every character is recorded. Even cursor movement, if you
@@ -2304,7 +2295,7 @@ Left Left
do I set the title?</a></h3>
<p>The control sequences for doing this are documented in
- <a href="xterm.faq.html#ctlseqs_ms">ctlseqs.ms</a>.</p>
+ <a href="#ctlseqs_ms">ctlseqs.ms</a>.</p>
<p>The usual context for this question is setting the title
according to the current working directory. People post answers
@@ -2449,166 +2440,162 @@ current_title=$(xprop -id $WINDOWID | grep WM_NAME | cut -d= -f2)
<p>Standard xterm does not implement a blinking cursor. Some of
the variations do: dtterm, GNOME Terminal, and modern xterm (from
- mid 1999, <a href="xterm.log.html#xterm_107">patch 107</a>).</p>
+ mid 1999, <a href="/xterm/xterm.log.html#xterm_107">patch
+ 107</a>).</p>
<h2 id="frequent_problems-id"><a name="frequent_problems" id=
"frequent_problems">Frequent problems</a></h2>
<ul>
<li>
- <a href="xterm.faq.html#problems_starting">Starting xterm, or
- not</a>
+ <a href="#problems_starting">Starting xterm, or not</a>
<ul>
- <li><a href="xterm.faq.html#no_ptys">Xterm does not run (no
- available pty's)</a></li>
+ <li><a href="#no_ptys">Xterm does not run (no available
+ pty's)</a></li>
- <li><a href="xterm.faq.html#no_termcap">I need
- /etc/termcap</a></li>
+ <li><a href="#no_termcap">I need /etc/termcap</a></li>
- <li><a href="xterm.faq.html#no_libpath">Why does
- $LD_LIBRARY_PATH get reset?</a></li>
+ <li><a href="#no_libpath">Why does $LD_LIBRARY_PATH get
+ reset?</a></li>
- <li><a href="xterm.faq.html#no_ls_and_e">Why do the -e and
- -ls options not work together?</a></li>
+ <li><a href="#no_ls_and_e">Why do the -e and -ls options
+ not work together?</a></li>
- <li><a href="xterm.faq.html#setup_resize">Why is my screen
- size not set?</a></li>
+ <li><a href="#setup_resize">Why is my screen size not
+ set?</a></li>
- <li><a href="xterm.faq.html#tiny_menus">Why are the menus
- tiny?</a></li>
+ <li><a href="#tiny_menus">Why are the menus tiny?</a></li>
</ul>
</li>
<li>
- <a href="xterm.faq.html#problems_fonts">Font problems</a>
+ <a href="#problems_fonts">Font problems</a>
<ul>
- <li><a href="xterm.faq.html#no_altchar">My terminal doesn't
- show box characters</a></li>
+ <li><a href="#no_altchar">My terminal doesn't show box
+ characters</a></li>
- <li><a href="xterm.faq.html#scaled_font">The bold font is
- ugly</a></li>
+ <li><a href="#scaled_font">The bold font is ugly</a></li>
- <li><a href="xterm.faq.html#little_dot">I see little dots
- on the screen</a></li>
+ <li><a href="#little_dot">I see little dots on the
+ screen</a></li>
- <li><a href="xterm.faq.html#no_russian">My terminal doesn't
- display Cyrillic characters</a></li>
+ <li><a href="#no_russian">My terminal doesn't display
+ Cyrillic characters</a></li>
- <li><a href="xterm.faq.html#utf8_fonts">I see boxes instead
- of characters in uxterm</a></li>
+ <li><a href="#utf8_fonts">I see boxes instead of characters
+ in uxterm</a></li>
- <li><a href="xterm.faq.html#slow_menus">The first popup
- menu is very slow</a></li>
+ <li><a href="#slow_menus">The first popup menu is very
+ slow</a></li>
</ul>
</li>
<li>
- <a href="xterm.faq.html#problems_keyboard">Keyboard
- problems</a>
+ <a href="#problems_keyboard">Keyboard problems</a>
<ul>
- <li><a href="xterm.faq.html#xterm_8bits">Why can't I input
- 8-bit characters?</a></li>
+ <li><a href="#xterm_8bits">Why can't I input 8-bit
+ characters?</a></li>
- <li><a href="xterm.faq.html#xterm_erase">Why doesn't my
- delete key work?</a></li>
+ <li><a href="#xterm_erase">Why doesn't my delete key
+ work?</a></li>
- <li><a href="xterm.faq.html#xterm_erased">Why did my delete
- key stop working?</a></li>
+ <li><a href="#xterm_erased">Why did my delete key stop
+ working?</a></li>
- <li><a href="xterm.faq.html#xterm_xmodmap">Well, how can I
- set my delete key?</a></li>
+ <li><a href="#xterm_xmodmap">Well, how can I set my delete
+ key?</a></li>
- <li><a href="xterm.faq.html#xterm_keypad">Why doesn't my
- keypad work?</a></li>
+ <li><a href="#xterm_keypad">Why doesn't my keypad
+ work?</a></li>
- <li><a href="xterm.faq.html#xterm_pageup">Why can't I use
- the pageup/pagedown keys?</a></li>
+ <li><a href="#xterm_pageup">Why can't I use the
+ pageup/pagedown keys?</a></li>
- <li><a href="xterm.faq.html#xterm_pc_style">Why can't I use
- the home/end keys?</a></li>
+ <li><a href="#xterm_pc_style">Why can't I use the home/end
+ keys?</a></li>
- <li><a href="xterm.faq.html#xterm_arrows">Why can't I use
- the cursor keys in (whatever) shell?</a></li>
+ <li><a href="#xterm_arrows">Why can't I use the cursor keys
+ in (whatever) shell?</a></li>
- <li><a href="xterm.faq.html#bash_meta_mode">Alt-keys do not
- work in bash</a></li>
+ <li><a href="#bash_meta_mode">Alt-keys do not work in
+ bash</a></li>
</ul>
</li>
<li>
- <a href="xterm.faq.html#problems_colors">Colors and other
- graphic rendition</a>
+ <a href="#problems_colors">Colors and other graphic
+ rendition</a>
<ul>
- <li><a href="xterm.faq.html#no_color">My terminal doesn't
- recognize color</a></li>
+ <li><a href="#no_color">My terminal doesn't recognize
+ color</a></li>
- <li><a href="xterm.faq.html#xterm_terminfo">What $TERM
- should I use?</a></li>
+ <li><a href="#xterm_terminfo">What $TERM should I
+ use?</a></li>
- <li><a href="xterm.faq.html#xterm_hilite">Reverse video is
- not reset</a></li>
+ <li><a href="#xterm_hilite">Reverse video is not
+ reset</a></li>
- <li><a href="xterm.faq.html#vim_16colors">My colors changed
- in vim</a></li>
+ <li><a href="#vim_16colors">My colors changed in
+ vim</a></li>
- <li><a href="xterm.faq.html#bold_vs_16colors">Aren't bright
- colors the same as bold?</a></li>
+ <li><a href="#bold_vs_16colors">Aren't bright colors the
+ same as bold?</a></li>
- <li><a href="xterm.faq.html#dont_like_blue">I don't like
- that shade of blue</a></li>
+ <li><a href="#dont_like_blue">I don't like that shade of
+ blue</a></li>
- <li><a href="xterm.faq.html#why_no_italics">Why doesn't
- xterm support italics?</a></li>
+ <li><a href="#why_no_italics">Why doesn't xterm support
+ italics?</a></li>
- <li><a href="xterm.faq.html#grep_colors">"grep --color"
- does not show the right output</a></li>
+ <li><a href="#grep_colors">"grep --color" does not show the
+ right output</a></li>
- <li><a href="xterm.faq.html#vt100_wrapping">That
- description of wrapping is odd, say more?</a></li>
+ <li><a href="#vt100_wrapping">That description of wrapping
+ is odd, say more?</a></li>
</ul>
</li>
<li>
- <a href="xterm.faq.html#problems_weird">Odd behavior</a>
+ <a href="#problems_weird">Odd behavior</a>
<ul>
- <li><a href="xterm.faq.html#xterm_paste">Why can't I
- cut/paste in xterm?</a></li>
+ <li><a href="#xterm_paste">Why can't I cut/paste in
+ xterm?</a></li>
- <li><a href="xterm.faq.html#xterm_tabs">Why can't I select
- tab-characters in xterm?</a></li>
+ <li><a href="#xterm_tabs">Why can't I select tab-characters
+ in xterm?</a></li>
- <li><a href="xterm.faq.html#xterm_resize">FVWM does weird
- things when I try to resize xterm</a></li>
+ <li><a href="#xterm_resize">FVWM does weird things when I
+ try to resize xterm</a></li>
- <li><a href="xterm.faq.html#xterm_tite">Why doesn't the
- screen clear when running vi?</a></li>
+ <li><a href="#xterm_tite">Why doesn't the screen clear when
+ running vi?</a></li>
- <li><a href="xterm.faq.html#xterm_form_feed">Why doesn't
- the screen clear when I type control/L?</a></li>
+ <li><a href="#xterm_form_feed">Why doesn't the screen clear
+ when I type control/L?</a></li>
- <li><a href="xterm.faq.html#xterm_vite">Why is the cursor
- misplaced after running vi?</a></li>
+ <li><a href="#xterm_vite">Why is the cursor misplaced after
+ running vi?</a></li>
- <li><a href="xterm.faq.html#narrowproto">Why doesn't the
- scrollbar work?</a></li>
+ <li><a href="#narrowproto">Why doesn't the scrollbar
+ work?</a></li>
- <li><a href="xterm.faq.html#window_ops">Why can't my
- program read the window title?</a></li>
+ <li><a href="#window_ops">Why can't my program read the
+ window title?</a></li>
- <li><a href="xterm.faq.html#window_ops2">Why can't my
- program set the window size?</a></li>
+ <li><a href="#window_ops2">Why can't my program set the
+ window size?</a></li>
- <li><a href="xterm.faq.html#compiz_bugs">Why is the text in
- the wrong place?</a></li>
+ <li><a href="#compiz_bugs">Why is the text in the wrong
+ place?</a></li>
</ul>
</li>
- <li><a href="xterm.faq.html#warning_msg">What is this warning
+ <li><a href="#warning_msg">What is this warning
message?</a></li>
</ul>
@@ -2868,10 +2855,11 @@ setenv COLUMNS 80</code>
the font.</p>
<p>Modern xterm can form its own line-drawing characters (see
- <a href="xterm.log.html#xterm_90">patch 90</a>, for example). It
- does not draw all of the graphic characters, only those that may
- be done with straight lines. But those are the most used, making
- most of the fixed-pitch fonts useful for xterm.</p>
+ <a href="/xterm/xterm.log.html#xterm_90">patch 90</a>, for
+ example). It does not draw all of the graphic characters, only
+ those that may be done with straight lines. But those are the
+ most used, making most of the fixed-pitch fonts useful for
+ xterm.</p>
<p>You may also have a problem with the terminfo description. As
distributed, the X11R6 terminfo for xterm does not have the
@@ -3128,13 +3116,13 @@ VT220 "remove" aka "delete" (ESC [ 3 ~)
(and an escape sequence from VT320) that changes this key between
the two styles (backspace or delete).</p>
- <p>With modern xterm <a href="xterm.log.html#xterm_95">patch
- 95</a> (also in the stable version as "88c"), you may have an
- xterm which can automatically initialize the backarrow key to
- backspace or delete depending on the pseudo terminal's sense, or
- based on the termcap setting of <em>kbs</em> (backspace key).
- This feature is controlled by the resource setting
- <em>ptyInitialErase</em>.</p>
+ <p>With modern xterm <a href=
+ "/xterm/xterm.log.html#xterm_95">patch 95</a> (also in the stable
+ version as "88c"), you may have an xterm which can automatically
+ initialize the backarrow key to backspace or delete depending on
+ the pseudo terminal's sense, or based on the termcap setting of
+ <em>kbs</em> (backspace key). This feature is controlled by the
+ resource setting <em>ptyInitialErase</em>.</p>
<h4 id="xterm_erased-id"><a name="xterm_erased" id=
"xterm_erased">Why did my delete key stop working?</a></h4>
@@ -3177,10 +3165,10 @@ appres XTerm
character. So low-level applications which check stty will not
work. I found that unsetting $TERMCAP before running would work,
but this was not a good solution. Someone pointed out (see
- <a href="xterm.log.html#xterm_129">patch 129</a>), that the
- problem really was because termcap <code>kD</code> should delete
- the character at the current position. So it cannot be the same
- as <code>stty erase</code>.</p>
+ <a href="/xterm/xterm.log.html#xterm_129">patch 129</a>), that
+ the problem really was because termcap <code>kD</code> should
+ delete the character at the current position. So it cannot be the
+ same as <code>stty erase</code>.</p>
<p>As a matter of fact, <code>stty erase</code> has to be a
single character, so <escape>[3~ would not work anyway.</p>
@@ -3332,33 +3320,80 @@ keycode 22 = 0xff08
</blockquote>
<p>I test the keyboard (for VT52/VT100/VT220) using <a href=
- "../vttest/vttest.html">vttest</a>. If you find (or think that
- you have found) a problem with the keyboard handling of xterm,
- please test it with vttest first.</p>
+ "/vttest/vttest.html">vttest</a>. If you find (or think that you
+ have found) a problem with the keyboard handling of xterm, please
+ test it with vttest first.</p>
<p>Other arrangements of the keyboard are possible of course. If
you prefer to use the top row of the numeric keypad as PF1
through PF4, you should do this using xterm's X resources.</p>
+ <p>In 2014, I noticed <a href=
+ "http://www.neilvandyke.org/racket-charterm/";>a comment</a>,
+ which relates to the PF1-PF4 assignment, but also to the use of
+ function-key modifiers.<br>
+ Because that is a digression, I have expanded it in a <a href=
+ "/xterm/xterm-function-keys.html">separate page</a>.</p>
+
<h4 id="xterm_pageup-id"><a name="xterm_pageup" id=
"xterm_pageup">Why can't I use the pageup/pagedown keys?</a></h4>
- <p>Some vendors, e.g,. Sun, have added key translations which
- make the pageup and pagedown keys talk to the xterm's scrollbar
- instead of your application. They did the same thing for the home
- and end keys, thereby obscuring a bug in <a href=
+ <p>Some vendors, e.g,. Sun, added key translations which make the
+ pageup and pagedown keys talk to the xterm's scrollbar instead of
+ your application. They did the same thing for the home and end
+ keys, thereby obscuring a bug in <a href=
"xterm.faq.html#bug_xterm_r6">xterm</a>.</p>
<p>You can override this by specifying your own translations in
- your resource file. Use the translations in</p>
+ your resource file. The issue was first noted with Solaris 2.5,
+ with the file given in two locations:</p>
<blockquote>
<pre>
/usr/lib/X11/app-defaults/XTerm
+/usr/openwin/lib/app-defaults
</pre>
</blockquote>
- <p>as a guide. The relevant section of the app-default file looks
+ <p>using a symbolic link to relate the two. Later releases of
+ Solaris, e.g., 8-10 omitted the former location.<br>
+ Solaris 11 provides modern xterm (<a href=
+ "/xterm/xterm.log.html#xterm_271">patch #271</a>), and does not
+ have this problem.</p>
+
+ <p>As of February 2014, I am able to verify that AIX and HPUX
+ have updated to modern xterm, e.g.,</p>
+
+ <ul>
+ <li><a href="/xterm/xterm.log.html#xterm_180">patch #180</a> on
+ HPUX 11.31,</li>
+
+ <li><a href="/xterm/xterm.log.html#xterm_222">patch #222</a> on
+ AIX 6.1 and 7.1,</li>
+ </ul>
+
+ <p>Older AIX and HPUX releases distributed the X Consortium
+ (1994) app-defaults file.</p>
+
+ <blockquote>
+ <p style="font-variant:small-caps">In updating this question in
+ February 2014, I noticed that IBM added their copyright notice
+ in AIX's copy of the app-defaults file in</p>
+
+ <blockquote>
+ <pre>
+/usr/lpp/X11/lib/X11/app-defaults
+</pre>
+ </blockquote>
+
+ <p style="font-variant:small-caps">There were no other changes
+ to the file. Someone at IBM blundered.<br>
+ In patch #252, I ensured that my copyright notice is on those
+ files (I am the sole author, and can do that).</p>
+ </blockquote>
+
+ <p>Use the translations in the system's app-defaults file as a
+ guide. The relevant section of the app-default file looks
like</p>
<blockquote>
@@ -3460,8 +3495,8 @@ keycode 22 = 0xff08
"xterm_pc_style">Why can't I use the home/end keys?</a></h4>
<p>This is a long story, unless you are referring to X Consortium
- <a href="xterm.faq.html#bug_xterm_r6">xterm</a>. That program is
- simply broken in this respect.</p>
+ <a href="#bug_xterm_r6">xterm</a>. That program is simply broken
+ in this respect.</p>
<p>At the beginning, when the home/end keys were fixed for modern
xterm (in early 1996), there was some discussion regarding what
@@ -3508,9 +3543,9 @@ ESC O F
easy reconfiguration to make a VT220 emulator), I added
popup-menu items to switch between the modes. With minor
refinements, this was the approach for about two years,
- culminating with the <a href="xterm.log.html#xterm_88">"stable"
- patch #88</a>, which is essentially the version distributed with
- XFree86 3.3.x.</p>
+ culminating with the <a href=
+ "/xterm/xterm.log.html#xterm_88">"stable" patch #88</a>, which is
+ essentially the version distributed with XFree86 3.3.x.</p>
<dl>
<dt><em>NOTE</em>:</dt>
@@ -3629,9 +3664,9 @@ ESC O F
</li>
</ul>
- <p><a href="XTerm-debian-88c">Here is a resource file</a> which I
- tested with xterm-88c, xterm-149 and xterm-158, using $TERM set
- to xterm-debian:</p>
+ <p><a href="/xterm/XTerm-debian-88c">Here is a resource file</a>
+ which I tested with xterm-88c, xterm-149 and xterm-158, using
+ $TERM set to xterm-debian:</p>
<blockquote>
<!--{{atr2html-->
@@ -3740,7 +3775,7 @@ ESC O F
"bash_meta_mode">Alt-keys do not work in bash</a></h4>
<p>See <a href=
- "../ncurses/ncurses.faq.html#bash_meta_mode">Alt-keys do not work
+ "/ncurses/ncurses.faq.html#bash_meta_mode">Alt-keys do not work
in bash</a>.</p>
<h3 id="problems_colors-id"><a name="problems_colors" id=
@@ -3763,12 +3798,12 @@ ESC O F
<p>Check the terminal description, to see if it is installed
properly, e.g., for <a href=
- "../ncurses/ncurses.faq.html#no_color">ncurses</a>, which uses
+ "/ncurses/ncurses.faq.html#no_color">ncurses</a>, which uses
terminfo.</p>
<p>Finally, some applications (that do not interface properly
with terminfo or termcap) may need the environment variable
- <a href="../ncurses/ncurses.faq.html#no_colorterm">$COLORTERM</a>
+ <a href="/ncurses/ncurses.faq.html#no_colorterm">$COLORTERM</a>
to be set.</p>
<h4 id="xterm_terminfo-id"><a name="xterm_terminfo" id=
@@ -3805,7 +3840,7 @@ ESC O F
the screen in a single color are more efficient on terminals that
support back color erase. Inevitably, there are tradeoffs and
issues with standardization of the feature as noted in the
- <a href="../ncurses/ncurses.faq.html#bce_mismatches">ncurses
+ <a href="/ncurses/ncurses.faq.html#bce_mismatches">ncurses
FAQ</a>. Unsurprisingly, ncurses supports xterm's behavior.</p>
<p>Curses libraries that support color know about
@@ -3820,7 +3855,7 @@ ESC O F
"xterm-color" description, those will be efficient – and
fortuitously work. However, slang (through version 1.4.0) did not
work properly for the terminals that xterm-color was designed
- for. See this <a href="../lynx/lynx-ncurses.html">page</a> for an
+ for. See this <a href="/lynx/lynx-ncurses.html">page</a> for an
example of (n)curses and slang running on dtterm. That bug in
slang is reported to be fixed for succeeding versions, though
your application may require changes to use this fix. (The demo
@@ -3867,7 +3902,7 @@ ESC O F
"vim_16colors">My colors changed in vim</a></h4>
<p>Some <code>vim</code> users may notice their colors change
- after updating to <a href="xterm.log.html#xterm_238">patch
+ after updating to <a href="/xterm/xterm.log.html#xterm_238">patch
238</a>. Before, some text would display in a dark color using a
bold font. Now, it displays in a bright color and normal
font.</p>
@@ -3880,10 +3915,10 @@ ESC O F
termcap does not match.</p>
<p>Vim also asks how many colors the terminal supports. Since
- <a href="xterm.log.html#xterm_148">patch 148</a>, xterm has
- responded with the number of distinct colors that it can display.
- By default, that is 16 (8 ANSI colors with bright counterparts
- for displaying PC-style "bold" text).</p>
+ <a href="/xterm/xterm.log.html#xterm_148">patch 148</a>, xterm
+ has responded with the number of distinct colors that it can
+ display. By default, that is 16 (8 ANSI colors with bright
+ counterparts for displaying PC-style "bold" text).</p>
<p>The interpretation of this depends on the application:
termcaps do not tell how to display more than 8 colors. But vim
Reply to: