xterm: Changes to 'debian-unstable'
debian/changelog | 9
debian/control | 6
debian/local/xterm.faq.html | 680 ++++++++++++++++++++++++++++++++++++++++++--
debian/rules | 4
4 files changed, 675 insertions(+), 24 deletions(-)
New commits:
commit 93fa5b89065dc12dea3c307f532a1c0dd07eb4e4
Author: Sven Joachim <svenjoac@gmx.de>
Date: Sat Dec 16 10:13:56 2017 +0100
Upload to unstable
diff --git a/debian/changelog b/debian/changelog
index 01eef93..1f1fc8c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-xterm (330-2) UNRELEASED; urgency=medium
+xterm (330-2) unstable; urgency=medium
* Add two simple autopkg smoke tests.
* Drop autotools-dev from Build-Depends, it is redundant now.
@@ -10,7 +10,7 @@ xterm (330-2) UNRELEASED; urgency=medium
* Bump Standards-Version to 4.1.2, no changes needed.
* Update copy of XTerm FAQ to revision 1.353 (dated 2017/11/11).
- -- Sven Joachim <svenjoac@gmx.de> Wed, 05 Jul 2017 22:58:37 +0200
+ -- Sven Joachim <svenjoac@gmx.de> Sat, 16 Dec 2017 10:13:24 +0100
xterm (330-1) unstable; urgency=medium
commit 84534c677be0fa6ae9cc724e76b5696ba74e560b
Author: Sven Joachim <svenjoac@gmx.de>
Date: Sat Dec 16 10:06:31 2017 +0100
Bump Standards-Version to 4.1.2
diff --git a/debian/changelog b/debian/changelog
index 5678639..01eef93 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,7 +7,7 @@ xterm (330-2) UNRELEASED; urgency=medium
* Switch from "dh_install --fail-missing" to "dh_missing --fail-missing".
* Look for tarballs on ftp.invisible-island.net in debian/watch.
* Set Rules-Requires-Root to no.
- * Bump Standards-Version to 4.1.1, no changes needed.
+ * Bump Standards-Version to 4.1.2, no changes needed.
* Update copy of XTerm FAQ to revision 1.353 (dated 2017/11/11).
-- Sven Joachim <svenjoac@gmx.de> Wed, 05 Jul 2017 22:58:37 +0200
diff --git a/debian/control b/debian/control
index 37c9c38..4bd0666 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: x11
Priority: optional
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Uploaders: Sven Joachim <svenjoac@gmx.de>
-Standards-Version: 4.1.1
+Standards-Version: 4.1.2
Rules-Requires-Root: no
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-xorg/app/xterm.git
Vcs-Git: https://anonscm.debian.org/git/pkg-xorg/app/xterm.git
commit 580ccf9ec567f85fb5c569c094675544493c728f
Author: Sven Joachim <svenjoac@gmx.de>
Date: Sat Dec 16 10:04:05 2017 +0100
Update copy of XTerm FAQ to revision 1.353 (dated 2017/11/11)
diff --git a/debian/changelog b/debian/changelog
index 14e2ece..5678639 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,6 +8,7 @@ xterm (330-2) UNRELEASED; urgency=medium
* Look for tarballs on ftp.invisible-island.net in debian/watch.
* Set Rules-Requires-Root to no.
* Bump Standards-Version to 4.1.1, no changes needed.
+ * Update copy of XTerm FAQ to revision 1.353 (dated 2017/11/11).
-- Sven Joachim <svenjoac@gmx.de> Wed, 05 Jul 2017 22:58:37 +0200
diff --git a/debian/local/xterm.faq.html b/debian/local/xterm.faq.html
index e31810d..82b86b9 100644
--- a/debian/local/xterm.faq.html
+++ b/debian/local/xterm.faq.html
@@ -1,6 +1,6 @@
<!--
*****************************************************************************
- * Copyright 1997-2015,2016 by Thomas E. Dickey *
+ * Copyright 1997-2016,2017 by Thomas E. Dickey *
* All Rights Reserved. *
* *
* Permission to use, copy, modify, and distribute this software and its *
@@ -19,7 +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.338 2017/04/08 14:00:16 tom Exp $
+ $XTermId: xterm.faq.html,v 1.353 2017/11/11 11:57:12 tom Exp $
-->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
@@ -402,8 +402,8 @@
"what_platforms">What platforms does it run on?</a></h2>
<p><strong>XTerm</strong> runs in all of the implementations of
- X11. I've built and run these since I started working on
- xterm:</p>
+ X11. As of 2000, I had built and run these since I started
+ working on xterm in 1996:</p>
<ul>
<li>AIX 3.2.5, 4.1, 4.3 (cc)</li>
@@ -427,9 +427,12 @@
<p>The older configurations have X11R5 libraries. Only minor
changes are needed to make xterm work on those systems. However,
- with X11R6 you can obtain better locale support, as well as new
- features such as the active icon. X11R7... not much to say
- there.</p>
+ X11R6 provided better locale support, as well as new features
+ such as the active icon. X11R7... not much to say there.</p>
+
+ <p>Since 2000, there have been a many changes (including new
+ platforms such as MacOS, NetBSD, OpenBSD, etc., as well as QNX,
+ Cygwin, and Minix).</p>
<h2 id="latest_version-id"><a name="latest_version" id=
"latest_version">What is the latest version?</a></h2>
@@ -439,8 +442,8 @@
<ul>
<li><a href=
- "ftp://invisible-island.net/xterm/xterm.tar.gz";>current source
- (ftp)</a></li>
+ "ftp://ftp.invisible-island.net/xterm/xterm.tar.gz";>current
+ source (ftp)</a></li>
<li><a href="/datafiles/release/xterm.tar.gz">current source
(http)</a></li>
@@ -2612,6 +2615,9 @@ current_title=$(xprop -id $WINDOWID | grep WM_NAME | cut -d= -f2)
<li><a href="#xaw_scrollbars">Can I improve the
scrollbars?</a></li>
+ <li><a href="#scroll_speed">Can I improve the scrolling
+ speed?</a></li>
+
<li><a href="#window_ops">Why can't my program read the
window title?</a></li>
@@ -2968,9 +2974,10 @@ setenv COLUMNS 80
"xterm.log.html#xterm_175">patch 175</a> to add an option
(<code>-k8</code>) and corresponding resource settings to allow
them to customize their environment. Here is a <a href=
- "ftp://invisible-island.net/xterm/koi8-term";>sample script</a>
- and <a href="ftp://invisible-island.net/xterm/KOI8Term";>resource
- file</a> which I use for testing this configuration.</p>
+ "ftp://ftp.invisible-island.net/xterm/koi8-term";>sample
+ script</a> and <a href=
+ "ftp://ftp.invisible-island.net/xterm/KOI8Term";>resource file</a>
+ which I use for testing this configuration.</p>
<h4 id="utf8_fonts-id"><a name="utf8_fonts" id="utf8_fonts">I see
boxes instead of characters in uxterm</a></h4>
@@ -4502,16 +4509,55 @@ XFree86 3.1.2a (23 September 1995)
copy of ITU T.416 (ISO-8613-6) which presumably clarified the
use of colon for this feature was costly.</p>
+ <p>Using semicolon was incorrect because some applications
+ could expect their parameters to be order-independent. As
+ used for the R/G/B values, that <em>was</em> order-dependent.
+ The relevant information, by the way, is part of ECMA-48 (not
+ ITU T.416, as mentioned in <a href=
+ "/ncurses/ncurses.faq.html#xterm_16MegaColors"><em>Why only
+ 16 (or 256) colors?</em></a>). Quoting from <a href=
+ "https://www.ecma-international.org/publications/files/ECMA-ST/Ecma-048.pdf";>
+ section 5.4.2 of ECMA-48, page 12</a>, and adding emphasis
+ (not in the standard):</p>
+
+ <blockquote>
+ <p class="code-block">Each parameter sub-string consists of
+ one or more bit combinations from 03/00 to
+ <strong>03/10</strong>; the bit combinations from 03/00 to
+ 03/09 represent the digits <em>ZERO</em> to <em>NINE</em>;
+ bit combination <strong>03/10</strong> may be used as a
+ separator in a <em>parameter sub-string</em>, for example,
+ to separate the fractional part of a decimal number from
+ the integer part of that number.</p>
+ </blockquote>
+
+ <p>and later on page 78, in 8.3.117 <em>SGR – SELECT
+ GRAPHIC RENDITION</em>, the description of SGR 38:</p>
+
+ <blockquote>
+ <p class="code-block">(reserved for future standardization;
+ intended for setting character foreground colour as
+ specified in ISO 8613-6 [CCITT Recommendation T.416])</p>
+ </blockquote>
+
+ <p>Of course you will immediately recognize that
+ <strong><tt>03/10</tt></strong> is ASCII <em>colon</em>, and
+ that ISO 8613-6 necessarily refers to the encoding in a
+ <em>parameter sub-string</em>. Or perhaps you will not.</p>
+
<p>It took several years for this to become an issue. The
developers of other terminal emulators were not the ones who
- first complained about it.</p>
+ first complained about it. In fact, though the
+ order-dependence was mentioned, no one pointed to a specific
+ program which was affected. Still, it was a known
+ problem.</p>
<p>Finally, in 2012 (<a href="/xterm/xterm.log.html">patch
#282</a>), I extended the parser to accommodate the "correct"
syntax. The original remains, simply because of its
widespread use. As before, it took a few years for other
terminal developers to notice and start incorporating the
- improvement. As of March 2016, not all have finished
+ improvement. As of March 2016, not all had finished
noticing.</p>
</li>
</ul>
@@ -5375,6 +5421,608 @@ configure --disable-imake --disable-narrowproto
initialization and operation. In the case of Motif, it had
nothing like the Athena widget set's popup menus.</p>
+ <h4 id="scroll_speed-id"><a name="scroll_speed" id=
+ "scroll_speed">Can I improve the scrolling speed?</a></h4>
+
+ <p>Several years ago (before 2010) there was a <a href=
+ "https://web.archive.org/web/20091210162250/https://martin.ankerl.com/2007/09/01/comprehensive-linux-terminal-performance-comparison/";>
+ webpage</a> which gave its author's notion of what constituted a
+ “good” terminal emulator:
+ <strong><code>cat</code></strong>'ing (sending) a large file to
+ the terminal would complete in minimal time. Apparently that was
+ the sole interest. Interestingly, its author stated that
+ <em>xterm</em> was the slowest although the presented data do not
+ show this. Also, although the page says “Linux” some
+ of the data are for programs running on
+ <strong><em>Windows</em></strong>. The page spawned a few
+ imitators (with no better methodology), none was systematic, none
+ did any analysis.</p>
+
+ <p>Of course, developers do not do that in practice. The terminal
+ is useful for interactive tasks. Compiling is best done by
+ redirecting the build messages to a log file or using a batch
+ process. End users have a different outlook.</p>
+
+ <p>There is more than one factor involved in scrolling speed.
+ Here are a few:</p>
+
+ <ul>
+ <li>
+ <p>When <strong>xterm</strong> was first written, machines
+ had less memory, and scrolling back a thousand lines seemed
+ good enough for users. Internally, <em>xterm</em> stored the
+ current screen and saved-lines in a large array. It scrolled
+ the array by shifting the entire array by a given number of
+ rows. For a thousand lines saved-lines (the scrollback
+ region), that works well enough.</p>
+
+ <p>But the <a href=
+ "manpage/xterm.html#VT100-Widget-Resources:saveLines"><code>saveLines</code></a>
+ resource allows a full <em>integer</em>, and during the
+ mid/late-1990s, a few users found that setting the resource
+ to a million lines made <em>xterm</em> very slow.</p>
+
+ <p>Still, the graphics display was fast enough. By the way,
+ <em>xterm</em> uses the <em>XCopyArea</em> function, and
+ normally (attempts to) display all of the updates to the
+ screen.</p>
+ </li>
+
+ <li>
+ <p>Later, <strong>rxvt</strong> came along. It limited the
+ number of saved-lines to a signed 16-bit integer, i.e., 32767
+ (and some packagers limited it to only a few thousand lines),
+ and moved just the pointers to the line data when scrolling
+ rather than shifting all of the text. It also uses
+ <em>XCopyArea</em>, noting in its features</p>
+
+ <blockquote>
+ <pre class="code-block">
+/*
+ * Define to remove support for XCopyArea() support. XCopyArea() is useful
+ * for scrolling on non-local X displays
+ */
+/* #define NO_SLOW_LINK_SUPPORT */
+</pre>
+ </blockquote>
+
+ <p>Unlike <em>xterm</em>, <em>rxvt</em> did not attempt to
+ display all updates. If it fell behind, it would discard some
+ of the updates, to catch up. Doing that had a greater effect
+ on the apparent scrolling speed than its internal memory
+ organization, since it was useful for any number of
+ saved-lines. One drawback was that ASCII animations were
+ somewhat erratic.</p>
+ </li>
+
+ <li>
+ <p>A few other terminal emulators, such as
+ <strong>konsole</strong> copied the <em>rxvt</em> feature.
+ Others copied, in turn, from whatever source. As a result,
+ one cannot compare the speed of different terminal emulators,
+ since they do not follow the same rules.</p>
+ </li>
+
+ <li>
+ <p>The issue with <em>xterm</em> shifting a large array was a
+ problem which was addressed by changing all of the pointers
+ to its line data into a <a href=
+ "http://www.geeksforgeeks.org/implementation-deque-using-circular-array/";>
+ <em>circular array</em></a> in 2009 (<a href=
+ "xterm.log.html#xterm_244">patch #244</a>).</p>
+ </li>
+
+ <li>
+ <p>Even after improving the memory performance of scrolling,
+ <em>rxvt</em> and its imitators still appeared to scroll
+ faster.</p>
+
+ <p>The <a href=
+ "manpage/xterm.html#VT100-Widget-Resources:fastScroll"><code>fastScroll</code></a>
+ resource added in patch #244 provides a simple implementation
+ of the <em>rxvt</em> (mis?)feature for <em>xterm</em>.</p>
+
+ <p>As implemented, it is rather crude (sometimes
+ <em>xterm</em> — like <em>konsole</em> — appears
+ to stop, since it is waiting for a new set of screen updates
+ after having discarded some).</p>
+ </li>
+ </ul>
+
+ <p>Scrolling speed is only one aspect of terminal speed, but it
+ is easy to measure. Other aspects (such as the speed with which
+ an application can change color, move the cursor around the
+ screen, write text in various places) can also be measured. But
+ comparing terminals based on that speed can be misleading. When
+ the terminal drops updates to keep up with an application's
+ speed, the result may be unnoticeable (if the application is fast
+ enough), or it may not.</p>
+
+ <p>For example, running the <strong>dots</strong> program from
+ the <a href="/ncurses/ncurses-examples.html">ncurses-examples</a>
+ shows some interesting misbehavior with <em>gnome-terminal</em>
+ and <em>konsole</em>: both “choke” at times for a few
+ seconds. The <em>dots</em> program prints colored cells randomly
+ around the screen, pausing briefly 1% of the time. However when
+ <em>dots</em> is terminated, it prints the program's notion of
+ the output rate. In spite of the pauses, the program saw a fairly
+ good rate of output. Some terminal emulators cannot keep up with
+ <em>dots</em>; one possible explanation for the discrepancy is
+ that the terminal emulator discards output (as in the special
+ case of scrolling).</p>
+
+ <p>Seeing that raised the question of what variation to expect
+ from different terminal emulators, to point out which might
+ discard output to achieve fast scrolling speeds. A simple script
+ showing the elapsed time to send <em>ncurses</em>'s <a href=
+ "/ncurses/terminfo.src.html"><code>terminfo.src</code></a>
+ (1.1Mb) a given number of times to the terminal was used. Here is
+ a table illustrating the differences, using the available
+ terminal emulators for Fedora 26 and Ubuntu 17 in November
+ 2017:</p>
+
+ <table border="1" summary="examples of scrolling speed">
+ <tr>
+ <th rowspan="2" style="width:6em;">Mode</th>
+
+ <th rowspan="2" style="width:10em;">Terminal</th>
+
+ <th colspan="3">Fedora</th>
+
+ <th colspan="3">Ubuntu</th>
+ </tr>
+
+ <tr>
+ <th style="width:4em;">1</th>
+
+ <th style="width:4em;">10</th>
+
+ <th style="width:4em;">99</th>
+
+ <th style="width:4em;">1</th>
+
+ <th style="width:4em;">10</th>
+
+ <th style="width:4em;">99</th>
+ </tr>
+
+ <tr>
+ <td rowspan="10" align="center">Remote</td>
+
+ <td>gnome-terminal</td>
+
+ <td>(1)</td>
+
+ <td>(1)</td>
+
+ <td>(1)</td>
+
+ <td>(1)</td>
+
+ <td>(1)</td>
+
+ <td>(1)</td>
+ </tr>
+
+ <tr>
+ <td>konsole</td>
+
+ <td>0.12</td>
+
+ <td>2.10</td>
+
+ <td>23.2</td>
+
+ <td>0.26</td>
+
+ <td>2.65</td>
+
+ <td>25.7</td>
+ </tr>
+
+ <tr>
+ <td>mlterm</td>
+
+ <td>(2)</td>
+
+ <td>(2)</td>
+
+ <td>(2)</td>
+
+ <td>0.30</td>
+
+ <td>3.07</td>
+
+ <td>30.4</td>
+ </tr>
+
+ <tr>
+ <td>pterm / putty</td>
+
+ <td>0.15</td>
+
+ <td>1.42</td>
+
+ <td>14.6</td>
+
+ <td>0.55</td>
+
+ <td>5.66</td>
+
+ <td>56.2</td>
+ </tr>
+
+ <tr>
+ <td>rxvt (3)</td>
+
+ <td>0.25</td>
+
+ <td>2.97</td>
+
+ <td>29.5</td>
+
+ <td>0.23</td>
+
+ <td>3.03</td>
+
+ <td>29.5</td>
+ </tr>
+
+ <tr>
+ <td>st / stterm (4)</td>
+
+ <td>0.07</td>
+
+ <td>0.50</td>
+
+ <td>4.40</td>
+
+ <td>0.15</td>
+
+ <td>1.42</td>
+
+ <td>14.4</td>
+ </tr>
+
+ <tr>
+ <td>terminology</td>
+
+ <td>0.10</td>
+
+ <td>1.00</td>
+
+ <td>10.1</td>
+
+ <td>0.19</td>
+
+ <td>2.01</td>
+
+ <td>19.0</td>
+ </tr>
+
+ <tr>
+ <td>urxvt</td>
+
+ <td>0.05</td>
+
+ <td>0.38</td>
+
+ <td>3.24</td>
+
+ <td>0.17</td>
+
+ <td>1.60</td>
+
+ <td>15.7</td>
+ </tr>
+
+ <tr>
+ <td>xterm</td>
+
+ <td>0.31</td>
+
+ <td>3.50</td>
+
+ <td>34.8</td>
+
+ <td>0.47</td>
+
+ <td>4.41</td>
+
+ <td>44.1</td>
+ </tr>
+
+ <tr>
+ <td>xterm + fastScroll</td>
+
+ <td>0.09</td>
+
+ <td>0.82</td>
+
+ <td>8.36</td>
+
+ <td>0.39</td>
+
+ <td>2.43</td>
+
+ <td>22.9</td>
+ </tr>
+
+ <tr>
+ <td rowspan="10" align="center">Local</td>
+
+ <td>gnome-terminal</td>
+
+ <td>0.12</td>
+
+ <td>1.16</td>
+
+ <td>11.4</td>
+
+ <td>0.29</td>
+
+ <td>3.14</td>
+
+ <td>30.6</td>
+ </tr>
+
+ <tr>
+ <td>konsole</td>
+
+ <td>0.11</td>
+
+ <td>0.82</td>
+
+ <td>7.97</td>
+
+ <td>0.22</td>
+
+ <td>2.17</td>
+
+ <td>20.1</td>
+ </tr>
+
+ <tr>
+ <td>mlterm</td>
+
+ <td>(2)</td>
+
+ <td>(2)</td>
+
+ <td>(2)</td>
+
+ <td>1.01</td>
+
+ <td>7.59</td>
+
+ <td>105.</td>
+ </tr>
+
+ <tr>
+ <td>pterm / putty</td>
+
+ <td>0.17</td>
+
+ <td>1.52</td>
+
+ <td>14.6</td>
+
+ <td>(5)</td>
+
+ <td>(5)</td>
+
+ <td>(5)</td>
+ </tr>
+
+ <tr>
+ <td>rxvt</td>
+
+ <td>1.23</td>
+
+ <td>11.9</td>
+
+ <td>118.</td>
+
+ <td>1.75</td>
+
+ <td>16.9</td>
+
+ <td>166.</td>
+ </tr>
+
+ <tr>
+ <td>st / stterm (4)</td>
+
+ <td>0.08</td>
+
+ <td>0.61</td>
+
+ <td>5.10</td>
+
+ <td>0.21</td>
+
+ <td>1.63</td>
+
+ <td>15.9</td>
+ </tr>
+
+ <tr>
+ <td>terminology</td>
+
+ <td>0.09</td>
+
+ <td>1.03</td>
+
+ <td>10.1</td>
+
+ <td>0.43</td>
+
+ <td>1.64</td>
+
+ <td>16.0</td>
+ </tr>
+
+ <tr>
+ <td>urxvt</td>
+
+ <td>0.07</td>
+
+ <td>0.53</td>
+
+ <td>4.52</td>
+
+ <td>0.26</td>
+
+ <td>2.41</td>
+
+ <td>23.7</td>
+ </tr>
+
+ <tr>
+ <td>xterm</td>
+
+ <td>1.77</td>
+
+ <td>18.5</td>
+
+ <td>178.</td>
+
+ <td>2.70</td>
+
+ <td>26.5</td>
+
+ <td>259.</td>
+ </tr>
+
+ <tr>
+ <td>xterm + fastScroll</td>
+
+ <td>0.12</td>
+
+ <td>0.96</td>
+
+ <td>9.92</td>
+
+ <td>0.25</td>
+
+ <td>2.36</td>
+
+ <td>22.9</td>
+ </tr>
+ </table>
+
+ <p><strong>Notes</strong>:</p>
+
+ <ol>
+ <li>
+ <p>On both systems, <em>gnome-terminal</em> failed to connect
+ remotely.</p>
+ </li>
+
+ <li>
+ <p>Fedora does not have <em>mlterm</em>.</p>
+ </li>
+
+ <li>
+ <p>On Ubuntu, the <em>urxvt</em> package hijacks the name
+ “rxvt”, so the <em>“rxvt”</em>
+ actually tested was <em>rxvt-xpm</em> from the rxvt 2.7.10
+ package.</p>
+ </li>
+
+ <li>
+ <p>Fedora has <em>st</em> 0.70, while Ubuntu has version
+ 0.60, which is a couple of years older.</p>
+ </li>
+
+ <li>
+ <p>Running locally on Ubuntu, <em>pterm</em> 0.70-1 dumped
+ core.</p>
+ </li>
+ </ol>
+
+ <p>Regarding the selection of terminal emulators:</p>
+
+ <ul>
+ <li>
+ <p>Keeping mind that this is an <em>xterm</em> FAQ, the Linux
+ console (and Windows console, and PuTTY running on Windows)
+ are off-topic.</p>
+ </li>
+
+ <li>
+ <p>The table mentions programs which at one time or another
+ have set <a href=
+ "/ncurses/ncurses.faq.html#xterm_generic"><code>TERM=xterm</code></a>.</p>
+
+ <p>The actual test does not rely upon the terminal
+ description, nor in fact on any terminal description. The
+ distinction was made for their relevance to this FAQ.</p>
+ </li>
+
+ <li>
+ <p>Given that, <em>rxvt</em> 2.7.10 is listed, as well as its
+ descendent <em>urxvt</em> (rxvt-unicode).</p>
+
+ <p>Other variations of <em>rxvt</em> (such as <em>aterm</em>
+ and <em>mrxvt</em>) were considered, but since much of the
+ related code is identical, not very interesting.</p>
+ </li>
+
+ <li>
+ <p>Both systems have several variants of the <em>skins</em>
+ for the VTE library, but for both systems, the developers
+ have a heavy bias in favor of the GNOME desktop. Comparing
+ the performance of the various skins would be pointless,
+ since not all are equally supported (due to the GNOME
+ developers' practice of making incompatible changes), and
+ would make an unbalanced comparison in any case.</p>
+ </li>
+
+ <li>
+ <p>The Unix port of PuTTY, <em>pterm</em> is listed. It uses
+ <em>GDK</em>.</p>
+ </li>
+ </ul>
+
+ <p>Interestingly, performance is better running remotely. In the
+ test, the machines are not identical:</p>
+
+ <ul>
+ <li>The <em>remote</em> system uses a Mac mini-server.</li>
+
+ <li>The Fedora system is a virtual machine using
+ Parallels.</li>
+
+ <li>The Ubuntu system is a virtual machine using Vmware
+ Fusion.</li>
+ </ul>
+
+ <p>Possibly displaying on the virtual machines does not perform
+ as well as via XQuartz. But that is a lot of difference to
+ explain. More likely, the local X server is performing badly on
+ some calls.</p>
+
+ <ul>
+ <li>
+ <p>For a while, <em>XCopyArea</em> was a problem, where the
+ Xorg hackers had degraded its performance radically. While
+ that might still be the underlying issue, <em>st</em> and
+ <em>urxvt</em> do use that function.</p>
+ </li>
+
+ <li>
+ <p>Another possibility is mentioned in <em><a href=
+ "#compiz_bugs">Why is the text in the wrong place?</a></em>
+ where the apparent root cause was a server feature which only
+ implemented parts of the X protocol.</p>
+ </li>
+ </ul>
+
+ <p>Using the <em>fastScroll</em> feature made <em>xterm</em>
+ performance comparable to the “desktop” applications.
+ But as usual, with performance data, your mileage may vary.</p>
+
<h4 id="window_ops-id"><a name="window_ops" id="window_ops">Why
can't my program read the window title?</a></h4>
@@ -7325,10 +7973,10 @@ tbl ctlseqs.ms | groff -ms >ctlseqs.ps
<ul>
<li><a href=
- "ftp://invisible-island.net/shuford/";>ftp://invisible-island.net/shuford/</a></li>
+ "ftp://ftp.invisible-island.net/shuford/";>ftp://invisible-island.net/shuford/</a></li>
<li><a href=
- "http://invisible-mirror.net/archives/shuford/";>http://invisible-mirror.net/archives/shuford/</a></li>
+ "https://invisible-mirror.net/archives/shuford/";>http://invisible-mirror.net/archives/shuford/</a></li>
</ul>
</li>
commit 812c75446536260772b3a75fdd4addf90f5400e0
Author: Sven Joachim <svenjoac@gmx.de>
Date: Sat Dec 16 09:57:54 2017 +0100
Switch to "dh_missing --fail-missing"
Avoid the nags by dh_install in the build log:
dh_install --fail-missing
dh_install: Please use dh_missing --list-missing/--fail-missing instead
dh_install: This feature will be removed in compat 12.
diff --git a/debian/changelog b/debian/changelog
index ebbd8ff..14e2ece 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,7 @@ xterm (330-2) UNRELEASED; urgency=medium
* Drop autotools-dev from Build-Depends, it is redundant now.
* Drop alternate build-dependency on lynx-cur.
* Stop passing --parallel to dh, already default in compat level 10.
+ * Switch from "dh_install --fail-missing" to "dh_missing --fail-missing".
* Look for tarballs on ftp.invisible-island.net in debian/watch.
* Set Rules-Requires-Root to no.
* Bump Standards-Version to 4.1.1, no changes needed.
diff --git a/debian/rules b/debian/rules
index e5d36b6..32e280e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -69,8 +69,8 @@ override_dh_auto_install:
install -m 644 termcap $(DEBTREEDIR)/usr/share/doc/xterm/xterm.termcap
install -m 644 terminfo $(DEBTREEDIR)/usr/share/doc/xterm/xterm.terminfo
-override_dh_install:
- dh_install --fail-missing
+override_dh_missing:
+ dh_missing --fail-missing
%:
dh $@ --builddirectory=build/
commit db2b3d1932f09495d21906a6e8f79cc22bda74e2
Author: Sven Joachim <svenjoac@gmx.de>
Date: Sat Dec 16 09:33:48 2017 +0100
Drop alternate build-dependency on lynx-cur
The lynx-cur transitional package has been removed from Debian.
diff --git a/debian/changelog b/debian/changelog
index 44a7502..ebbd8ff 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,7 @@ xterm (330-2) UNRELEASED; urgency=medium
* Add two simple autopkg smoke tests.
* Drop autotools-dev from Build-Depends, it is redundant now.
+ * Drop alternate build-dependency on lynx-cur.
* Stop passing --parallel to dh, already default in compat level 10.
* Look for tarballs on ftp.invisible-island.net in debian/watch.
* Set Rules-Requires-Root to no.
diff --git a/debian/control b/debian/control
index a9e0519..37c9c38 100644
--- a/debian/control
+++ b/debian/control
@@ -18,7 +18,7 @@ Build-Depends:
libxinerama-dev,
debhelper (>= 10),
autoconf-dickey (>= 2.52+20170501),
- lynx | lynx-cur,
+ lynx,
xorg-docs-core,
desktop-file-utils,
@@ -107,7 +107,7 @@ Build-Depends:
# detect
# debhelper (>= 10) debian/compat = 10
# autoconf-dickey regenerate configure
-# lynx | lynx-cur generates plain-text version of xterm faq
+# lynx generates plain-text version of xterm faq
# desktop-file-utils for installing xterm.desktop
Package: xterm
Reply to: