Subject: xterm: uses unescaped backslashes in manpage example
Date: Sat, 08 May 2021 04:21:32 +0200
Package: xterm
Version: 366-1
Severity: minor
Tags: upstream
X-Debbugs-Cc: [email protected]
The manual page includes example commands such as…
printf '\033]2;Hello world!\033\'
… which use unescaped backslashes at the end of the command.
In general this works…
$ printf '\' | hd
00000000 5c |\|
… but when copying this specific example into a larger string,
such as appending “abc”, it fails:
$ printf '\abc' | hd
00000000 07 62 63 |.bc|
Doubling the backslash fixes this:
$ printf '\\abc' | hd
00000000 5c 61 62 63 |\abc|
In the manpage, this will mean changing the sequence “\e'” to
“\e\e'” (as each ‘\e’ denotes a backslash in nroff escaping).
-- System Information:
Debian Release: 11.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-4-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages xterm depends on:
ii libc6 2.31-12
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libice6 2:1.0.10-1
ii libtinfo6 6.2+20201114-2
ii libutempter0 1.2.1-2
ii libx11-6 2:1.7.0-2
ii libxaw7 2:1.0.13-1.1
ii libxext6 2:1.3.3-1.1
ii libxft2 2.3.2-2
ii libxinerama1 2:1.1.4-2
ii libxmu6 2:1.1.2-2+b3
ii libxpm4 1:3.5.12-1
ii libxt6 1:1.2.0-1
ii xbitmaps 1.1.1-2.1
Versions of packages xterm recommends:
ii x11-utils 7.7+5
Versions of packages xterm suggests:
pn xfonts-cyrillic <none>
-- no debconf information
On Sat, May 08, 2021 at 04:21:32AM +0200, Thorsten Glaser wrote:
> Package: xterm
> Version: 366-1
> Severity: minor
> Tags: upstream
> X-Debbugs-Cc: [email protected]
>
> The manual page includes example commands such as…
>
> printf '\033]2;Hello world!\033\'
>
> … which use unescaped backslashes at the end of the command.
>
> In general this works…
>
> $ printf '\' | hd
> 00000000 5c |\|
>
> … but when copying this specific example into a larger string,
The example is correct, however. xterm's manpage isn't a tutorial
on shell programming.
--
Thomas E. Dickey <[email protected]>
https://invisible-island.netftp://ftp.invisible-island.net
Acknowledgement sent
to Thorsten Glaser <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <[email protected]>.
(Sat, 08 May 2021 19:57:05 GMT) (full text, mbox, link).
Subject: Re: Bug#988221: xterm: uses unescaped backslashes in manpage example
Date: Sat, 8 May 2021 19:44:13 +0000 (UTC)
Thomas Dickey dixit:
>The example is correct, however. xterm's manpage isn't a tutorial
>on shell programming.
Yes and yes, but it’s still over-microoptimised, in a way that is
not helpful to users.
bye,
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
Source: xterm
Source-Version: 371-1
Done: Sven Joachim <[email protected]>
We believe that the bug you reported is fixed in the latest version of
xterm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sven Joachim <[email protected]> (supplier of updated xterm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 03 Mar 2022 18:27:23 +0100
Source: xterm
Architecture: source
Version: 371-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force <[email protected]>
Changed-By: Sven Joachim <[email protected]>
Closes: 904572988221
Changes:
xterm (371-1) unstable; urgency=medium
.
* New upstream release.
- Fix errata in manual page (Closes: #988221).
* Drop patch from 370-2, applied upstream.
* Prefer luit over x11-utils in Recommends (Closes: #904572).
* Update copy of XTerm FAQ to revision 1.407 (dated 2021/12/20).
* Update years in debian/copyright.
Checksums-Sha1:
726c915aa364ef2eb3b9b758bc5b0ec50fd47df5 2449 xterm_371-1.dsc
34a6886e2477bbee3300af20590f3eb263f0ca8d 1507938 xterm_371.orig.tar.gz
24930ded74fdaa03dd563e9c66ab13bb4ee101ca 729 xterm_371.orig.tar.gz.asc
a62f283e17f066c078580a012cf9b49b2b082090 116480 xterm_371-1.debian.tar.xz
b2b123f81deebe1fc1b47ebceb762656761073a8 7672 xterm_371-1_source.buildinfo
Checksums-Sha256:
81f5e110295b83d4135c728cc6bdb9a9265eb1759d53894e069d322b64d43aab 2449 xterm_371-1.dsc
32f888277b19e28ebc0a3112bff000607c07bed0679caa0beebb36f9cad484f5 1507938 xterm_371.orig.tar.gz
a4a02d23a801adc63849762c0f1749cca1b224b824184ffd59058196ebf73a32 729 xterm_371.orig.tar.gz.asc
fb9ab378187c7e1f109947d191764e0f9edfc60d64e31005c8917bf9ce53a08c 116480 xterm_371-1.debian.tar.xz
c1f2757cf536ff4f6f920db78031103b9d4d3d64d9ec3e09393014f84b2f014b 7672 xterm_371-1_source.buildinfo
Files:
f35174e9902549e8cbe90a0d6a57e6f8 2449 x11 optional xterm_371-1.dsc
69c8db0b721b280266fb0dec879a4a3d 1507938 x11 optional xterm_371.orig.tar.gz
73d7968cd7324583842748f65cb5619b 729 x11 optional xterm_371.orig.tar.gz.asc
dc338d7ff4ae6f0bab68c4200df44270 116480 x11 optional xterm_371-1.debian.tar.xz
bab5c28f76d15d7db624f4cc66eabbb7 7672 x11 optional xterm_371-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEKF8heKgv5Jai5p4QOxBucY1rMawFAmIg+ssACgkQOxBucY1r
MaxgeQ/9HDgc2MqYha7VKmQxwvnR0dPKKedbA9vCS62PpVROulKknNR1gF55oA1C
UPT3pElv8URTeVJbawCQGTEw3zwuApQiieYXxSh9BHnBg4TykNRXiJbxlDq3HlYh
OU1+KXFO1ZiqvwEATLVQ2Hfv3lGOQvmUNdb7R/llqOX1Dcm8vpvm3iHeB/diPwcL
scJ1dyLGSlDgQ4gG3bpU617tgQrufTTGIskEndFROjGotM9a3rx717gZHNF29vdQ
PAQIdUczzghTrxFibYWtMqediZc3Uun2SbfXyknc3efGLeclFUZ8LZXsaj6yXIfz
mKZ4z7TD5AZDp99B1PmI6mwJMzJaaJ3sfkEozghg0t4cq592THZbEKndvcCF4LdN
wVu8EkizT6rgPv2ZfbptOJfcJn4TcaMf7wP5pE5p8r6kSrC6IrfEMydZ1wTDJGJ8
KoKSJP9ZhNKiMOizEHOtlm0Mw/HwW5gWTMcrQQ9BdzrE5c7LT/V1iD6ZfSVnjfvJ
tj4u9xqycmAeYiPUrWmf5g6bQu6kqBHcOxz4cAQOUZYScrY4HbylQSQR3mXYZ3nm
bwxlP5zh640c9HgIKFyk1X5cmiQNC8wfLscHTw0OGLlEQfdZh/msV3qJBWJKWANb
LhUnerLy8lL++9NCUFQUyM1nE+o1ecwSdbqUmdN4GgIL2NRPWb8=
=F703
-----END PGP SIGNATURE-----