Your message dated Sat, 21 Jun 2008 12:15:47 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: Fault is in the terminfo description
has caused the Debian Bug report #144178,
regarding screen: alternate character escapes not correct
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
144178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144178
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: screen
Version: 3.9.11-5
Severity: normal
The sequences to shift to and from the alternate character set (terminfo
names: smacs & rmacs) are defined in ncurses' terminfo for screen as ^N
and ^O respectively.
Unfortunatley screen only understands \E(0 and \E(B. It also emits these
sequences to instruct the terminal its running in to move in/out of the
ACS. This is wrong at least when running with TERM=xterm, as infocmp
shows that the correct sequences for this terminal type are ^N/^O.
xterm (the original) is liberal and will still switch character sets,
gnome-terminal (and maybe other clones) are more strict and only accept
the standard sequences.
-- System Information
Debian Release: 3.0
Kernel Version: Linux baal.assist.internet-security.at 2.4.18-ipsec-crypto #1
Mon Apr 15 14:36:33 CEST 2002 i686 unknown
Versions of the packages screen depends on:
ii base-passwd 3.4.1 Debian Base System Password/Group Files
ii debconf 1.0.32 Debian configuration management system
ii libc6 2.2.5-4 GNU C Library: Shared libraries and Timezone
ii libncurses5 5.2.20020112a- Shared libraries for terminal handling
ii libpam0g 0.72-35 Pluggable Authentication Modules library
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
An excellent description of why this is not a bug is on the screen-devel
mailing list:
http://lists.gnu.org/archive/html/screen-devel/2008-06/msg00020.html
Summary: before one can expect smacs and rmacs to do something special,
one must send enacs. terminfo(5) doesn't make this particularly clear,
but the Open Group's XCurses standard does.
Cheers!
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer,
and GNU Wget Project Maintainer.
http://micah.cowan.name/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIXVNj7M8hyUobTrERAsa1AJ9SOR6ucQTj/lZqrj5vZ/St3qR5gQCfTXYj
quHym3alLd+71iOk8wgIur0=
=D1fv
-----END PGP SIGNATURE-----
--- End Message ---
