[Git][xorg-team/app/xterm][debian-unstable] 2 commits: Update copy of XTerm FAQ to revision 1.432 (dated 2025/04/07)

Sven Joachim pushed to branch debian-unstable at X Strike Force / app / xterm


Commits:
ee8abff8 by Sven Joachim at 2026-04-16T18:47:00+02:00
Update copy of XTerm FAQ to revision 1.432 (dated 2025/04/07)

Still no new revision, but a few typos have been fixed.

- - - - -
2bad9e2f by Sven Joachim at 2026-04-16T18:51:47+02:00
Upload to unstable

- - - - -


2 changed files:

- debian/changelog
- debian/local/xterm.faq.html


Changes:

=====================================
debian/changelog
=====================================
@@ -1,12 +1,13 @@
-xterm (409-1) UNRELEASED; urgency=medium
+xterm (409-1) unstable; urgency=medium
 
   * New upstream release.
      - Improve feature which retains selection/highlighting when screen
        is scrolled (Closes: #1128961, see #291787).
      - Fill in a few more special cases for #1123877 (Closes: #1123877).
   * Bump Standards-Version to 4.7.4, no changes needed.
+  * Update copy of XTerm FAQ to revision 1.432 (dated 2025/04/07).
 
- -- Sven Joachim <[email protected]>  Wed, 15 Apr 2026 17:01:25 +0200
+ -- Sven Joachim <[email protected]>  Thu, 16 Apr 2026 18:51:19 +0200
 
 xterm (407-1) unstable; urgency=medium
 


=====================================
debian/local/xterm.faq.html
=====================================
@@ -643,7 +643,7 @@ lawsuit? [cite]
   and because well-behaved VT100 applications would not use
   features from higher-level terminals it was not initially
   important to prevent use of those by applications which assumed
-  they were using just a VT100. Knowledgable users could easily
+  they were using just a VT100. Knowledgeable users could easily
   configure xterm to emulate a VT220. In <a href=
   "xterm.log.html#xterm_280">2012</a>, I changed the default from
   VT100 to VT420.</p>
@@ -1003,7 +1003,7 @@ lawsuit? [cite]
   <p>Several of these programs are claimed (either by their
   developers, or their users) to emulate &ldquo;most&rdquo; of
   xterm. To me, &ldquo;most&rdquo; would be something quantifiable,
-  e.g., 80 percent. To satisfy my curiousity, I wrote a script to
+  e.g., 80 percent. To satisfy my curiosity, I wrote a script to
   extract the control sequence information from <a href=
   "xterm.faq.html#ctlseqs_ms">ctlseqs.txt</a>. This counts each
   control sequence, as well as the variations such as setting bold,
@@ -7060,13 +7060,13 @@ configure --disable-imake --disable-narrowproto
 
   <p>The longstanding control sequence for reading the window title
   is something that can be abused in special conditions. For novice
-  (unknowledgable) users, this can be a problem.</p>
+  (unknowledgeable) users, this can be a problem.</p>
 
   <p><strong>XTerm</strong> provides resource-settings and menu
   entries to allow this and related features to be enabled or
   disabled. See for example <code>allowWindowOps</code> The default
   resource settings in xterm can be overridden by a packager.
-  However, a knowledgable user can override those default
+  However, a knowledgeable user can override those default
   settings.</p>
 
   <p>It is also possible that an overzealous packager may have
@@ -7101,7 +7101,7 @@ configure --disable-imake --disable-narrowproto
   September 2012), but is less frequent. But it was an issue with
   Ubuntu since 2008.</p>
 
-  <p>There ware several related symptoms, e.g.,</p>
+  <p>There were several related symptoms, e.g.,</p>
 
   <ul>
     <li>



View it on GitLab: https://salsa.debian.org/xorg-team/app/xterm/-/compare/4e7c114421f923f3122e3d446555351b0ef81bd6...2bad9e2ff5ed7973bc3fd86558f4a4b14e80e9f2

-- 
View it on GitLab: https://salsa.debian.org/xorg-team/app/xterm/-/compare/4e7c114421f923f3122e3d446555351b0ef81bd6...2bad9e2ff5ed7973bc3fd86558f4a4b14e80e9f2
You're receiving this email because of your account on salsa.debian.org.