Your message dated Thu, 19 Jun 2008 16:47:47 -0700 with message-id <[EMAIL PROTECTED]> has caused the report #144178, regarding screen: alternate character escapes not correct to be marked as having been forwarded to the upstream software author(s) Robert Bihlmeyer <[EMAIL PROTECTED]>
(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 --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 tags: upstream It looks to me as if the fault is in the terminfo description for screen. Screen does in fact understand ^N/^O, and processes them according to ISO-2022. It does not simply pass them through, but rather processes them itself, to invoke the G1 character set to GL. However, screen's default value for "charset" is "BBBB02", which uses US-ASCII as the G1 character set. Setting it to "B0BB02" uses the box-drawing characters for G1, which would cause ^N/^O to behave as you expect them to (and would render the terminfo description accurately). Another way to invoke the box-drawing character set to G1 would be: $ printf '\033)0' (Note the ')', rather than '('). That would cause no immediately visible change, but ^N/^O would start working as you expect. Note that, if you're running in UTF-8 mode, screen apparently uses the Unicode box characters, rather than the parent terminal's smacs feature. So, to sum up, either the terminfo description (and screen's $TERMCAP) should specify '\E(0' / '\E)B', or else screen should default to "B0BB02" for the value of "charset". Forwarded upstream to: https://savannah.gnu.org/bugs/index.php?23646 - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer, and GNU Wget Project Maintainer. http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIWvAj7M8hyUobTrERAoDxAJ4xKSoQiTwBY1qyX6mkDVhZslVvwwCggQLq n5ZWEWcxDW4Bit4BWbZdkdc= =yFe2 -----END PGP SIGNATURE-----
--- End Message ---
